Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751491AbdFFJFs (ORCPT ); Tue, 6 Jun 2017 05:05:48 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48768 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751246AbdFFJFp (ORCPT ); Tue, 6 Jun 2017 05:05:45 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 480CF87649 Authentication-Results: ext-mx02.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx02.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=eguan@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 480CF87649 Date: Tue, 6 Jun 2017 17:05:42 +0800 From: Eryu Guan To: Jeff Layton Cc: fstests@vger.kernel.org, Andrew Morton , Al Viro , Jan Kara , tytso@mit.edu, axboe@kernel.dk, mawilcox@microsoft.com, ross.zwisler@linux.intel.com, corbet@lwn.net, dhowells@redhat.com, linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [xfstests PATCH v3 3/5] generic: test writeback error handling on dmerror devices Message-ID: <20170606090542.GP19952@eguan.usersys.redhat.com> References: <20170531130820.17634-1-jlayton@redhat.com> <20170531130820.17634-4-jlayton@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170531130820.17634-4-jlayton@redhat.com> User-Agent: Mutt/1.8.0 (2017-02-23) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Tue, 06 Jun 2017 09:05:44 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3748 Lines: 126 On Wed, May 31, 2017 at 09:08:18AM -0400, Jeff Layton wrote: > Ensure that we get an error back on all fds when a block device is > open by multiple writers and writeback fails. > > Signed-off-by: Jeff Layton > --- > tests/generic/998 | 64 +++++++++++++++++++++++++++++++++++++++++++++++++++ > tests/generic/998.out | 2 ++ > tests/generic/group | 1 + > 3 files changed, 67 insertions(+) > create mode 100755 tests/generic/998 > create mode 100644 tests/generic/998.out > > diff --git a/tests/generic/998 b/tests/generic/998 > new file mode 100755 > index 000000000000..fbadb47507c2 > --- /dev/null > +++ b/tests/generic/998 > @@ -0,0 +1,64 @@ > +#! /bin/bash > +# FS QA Test No. 998 > +# > +# Test writeback error handling when writing to block devices via pagecache. > +# See src/fsync-err.c for details of what test actually does. > +# > +#----------------------------------------------------------------------- > +# Copyright (c) 2017, Jeff Layton > +# > +# This program is free software; you can redistribute it and/or > +# modify it under the terms of the GNU General Public License as > +# published by the Free Software Foundation. > +# > +# This program is distributed in the hope that it would be useful, > +# but WITHOUT ANY WARRANTY; without even the implied warranty of > +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the > +# GNU General Public License for more details. > +# > +# You should have received a copy of the GNU General Public License > +# along with this program; if not, write the Free Software Foundation, > +# Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA > +#----------------------------------------------------------------------- > + > +seq=`basename $0` > +seqres=$RESULT_DIR/$seq > +echo "QA output created by $seq" > + > +here=`pwd` > +tmp=/tmp/$$ > +status=1 # failure is the default! > +trap "_cleanup; exit \$status" 0 1 2 3 15 > + > +_cleanup() > +{ > + cd / > + rm -rf $tmp.* $testdir > + _dmerror_cleanup > +} > + > +# get standard environment, filters and checks > +. ./common/rc > +. ./common/filter > +. ./common/dmerror > + > +# real QA test starts here > +_supported_os Linux > +_require_scratch _require_scratch_nocheck Then we don't have to re-create a filesystem on SCRATCH_DEV before exiting. > +_require_logdev > +_require_dm_target error > +_require_test_program fsync-err > + > +rm -f $seqres.full > + > +$XFS_IO_PROG -d -c "pwrite -S 0x7c -b 1048576 0 $((64 * 1048576))" $SCRATCH_DEV >> $seqres.full I don't see why this is needed, add some comments? Or remove it if it's not needed? > +_dmerror_init > + > +$here/src/fsync-err $DMERROR_DEV > + > +# success, all done > +_dmerror_load_working_table > +_dmerror_cleanup > +_scratch_mkfs > $seqres.full 2>&1 > +status=0 > +exit > diff --git a/tests/generic/998.out b/tests/generic/998.out > new file mode 100644 > index 000000000000..658c438820e2 > --- /dev/null > +++ b/tests/generic/998.out > @@ -0,0 +1,2 @@ > +QA output created by 998 > +Test passed! > diff --git a/tests/generic/group b/tests/generic/group > index 39f7b14657f1..9fc384363ca7 100644 > --- a/tests/generic/group > +++ b/tests/generic/group > @@ -440,4 +440,5 @@ > 435 auto encrypt > 436 auto quick rw > 437 auto quick > +998 auto quick This is a test for block device, not filesystems, I'd remove it from auto and quick group, but add it to 'blockdev' group. So it won't be run if someone wants to test filesystems. Thanks, Eryu > 999 auto quick > -- > 2.9.4 > > -- > To unsubscribe from this list: send the line "unsubscribe fstests" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html