generic/173: don't dump core when mwrite fails
authorDarrick J. Wong <darrick.wong@oracle.com>
Wed, 30 Aug 2017 22:31:10 +0000 (15:31 -0700)
committerEryu Guan <eguan@redhat.com>
Sun, 3 Sep 2017 04:20:00 +0000 (12:20 +0800)
commitd2f2947517aed99bbb8d268650083ae1aff323f0
treeb23f419eba6667b2e13151887ccac34cdec071c0
parentb669b303d02e39a62a212b87f4bd1ce259f73d10
generic/173: don't dump core when mwrite fails

In generic/173, we try to force a CoW to a mmap'd region to fail if
there's no space to actually stage the CoW operation.  That failure
comes in the form of a SIGBUS to xfs_io.  If the tester just happens
to have a nonzero coresize ulimit set, a core dump is generated and
the test is marked as having failed, even though the dump generation
is exactly the correct behavior.

Therefore, set the coresize ulimit to zero while calling
_mwrite_byte.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Reviewed-by: Eryu Guan <eguan@redhat.com>
Signed-off-by: Eryu Guan <eguan@redhat.com>
tests/generic/173