public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] xfs: Regression test for invalid sb_logsunit
Date: Fri, 12 Jan 2018 09:58:51 +0800	[thread overview]
Message-ID: <5A58165B.9010706@cn.fujitsu.com> (raw)
In-Reply-To: <20180111180734.GD1168@magnolia>

Hi Darrick,

Thanks for your comment, i will send v2 patch based on 
_scratch_xfs_[get|set]_sb_field helper. :-)

On 2018/01/12 2:07, Darrick J. Wong wrote:
> On Thu, Jan 11, 2018 at 04:25:08PM +0800, xiao yang wrote:
>> If log stripe unit isn't a multiple of the fs blocksize and mounting,
>> the invalid sb_logsunit leads to crash as soon as we try to write to
>> the log.
>>
>> Signed-off-by: xiao yang<yangx.jy@cn.fujitsu.com>
>> ---
>>   tests/xfs/437     | 73 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>   tests/xfs/437.out |  2 ++
>>   tests/xfs/group   |  1 +
>>   3 files changed, 76 insertions(+)
>>   create mode 100755 tests/xfs/437
>>   create mode 100644 tests/xfs/437.out
>>
>> diff --git a/tests/xfs/437 b/tests/xfs/437
>> new file mode 100755
>> index 0000000..96cec25
>> --- /dev/null
>> +++ b/tests/xfs/437
>> @@ -0,0 +1,73 @@
>> +#! /bin/bash
>> +# FS QA Test No. 437
>> +#
>> +# Regression test for commit:
>> +# 9c92ee2 ("xfs: validate sb_logsunit is a multiple of the fs blocksize")
>> +#
>> +# If log stripe unit isn't a multiple of the fs blocksize and mounting,
>> +# the invalid sb_logsunit leads to crash as soon as we try to write to
>> +# the log.
>> +#
>> +#-----------------------------------------------------------------------
>> +# Copyright (c) 2018 FUJITSU.  All Rights Reserved.
>> +# Author: Xiao Yang<yangx.jy@cn.fujitsu.com>
>> +#
>> +# 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()
>> +{
>> +	rm -rf $tmp.*
>> +}
>> +
>> +# get standard environment and checks
>> +. ./common/rc
>> +
>> +# real QA test starts here
>> +_supported_os Linux
>> +_supported_fs xfs
>> +_require_scratch
>> +
>> +rm -f "$seqres.full"
>> +
>> +# Format
>> +_scratch_mkfs>  $seqres.full 2>&1 || _fail "mkfs failed"
>> +
>> +# Set logsunit to a value which is not a multiple of the fs blocksize
>> +blksz=$(_scratch_xfs_db -x -c "sb 0" -c "p blocksize")
> _scratch_xfs_get_metadata_field ?
>
> (Or, _scratch_xfs_get_sb_field if Hou Tao's dquot unmount tests go in)
Agreed.  Use _scratch_xfs_get_sb_field here.
>> +_scratch_xfs_db -x -c "sb 0" -c "write logsunit $((blksz - 1))" \
>> +	>>  $seqres.full 2>&1 || _notrun "Failed to set sb_logsunit"
> _scratch_xfs_set_metadata_field ?
Agreed.  Use _scratch_xfs_set_sb_field here.

Thanks,
Xiao Yang
> Otherwise this looks decent.
>
> --D
>> +
>> +# Mount and writing log may trigger a crash
>> +if _scratch_mount>>  $seqres.full 2>&1; then
>> +	for i in $(seq 1 1000); do
>> +		touch ${SCRATCH_MNT}/$i
>> +	done
>> +	_scratch_unmount
>> +fi
>> +
>> +echo "Silence is golden"
>> +
>> +# success, all done
>> +status=0
>> +exit
>> diff --git a/tests/xfs/437.out b/tests/xfs/437.out
>> new file mode 100644
>> index 0000000..4dcb607
>> --- /dev/null
>> +++ b/tests/xfs/437.out
>> @@ -0,0 +1,2 @@
>> +QA output created by 437
>> +Silence is golden
>> diff --git a/tests/xfs/group b/tests/xfs/group
>> index d230060..35d1b03 100644
>> --- a/tests/xfs/group
>> +++ b/tests/xfs/group
>> @@ -434,3 +434,4 @@
>>   434 auto quick clone fsr
>>   435 auto quick clone
>>   436 auto quick clone fsr
>> +437 auto quick log dangerous
>> -- 
>> 1.8.3.1
>>
>>
>>
>
> .
>




  reply	other threads:[~2018-01-12  1:59 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11  8:25 [PATCH] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-11 18:07 ` Darrick J. Wong
2018-01-12  1:58   ` Xiao Yang [this message]
2018-01-12  6:14   ` [PATCH v2] syscalls/madvise09.c: Use custom mount point instead of /sys/fs/cgroup/memory xiao yang
2018-01-12  6:14     ` [PATCH v2] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-12  6:19     ` [PATCH v2] syscalls/madvise09.c: Use custom mount point instead of /sys/fs/cgroup/memory Xiao Yang
2018-01-12  6:16   ` [PATCH v2 1/2] common/xfs: Check if write supports [-c|-d] option in xfs_db xiao yang
2018-01-12  6:16     ` [PATCH v2 2/2] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-12  7:49       ` Eryu Guan
2018-01-12  8:36         ` Dave Chinner
2018-01-12  8:50           ` Eryu Guan
2018-01-12 16:41             ` Darrick J. Wong
2018-01-13  2:23             ` Dave Chinner
2018-01-15  6:29               ` Eryu Guan
2018-01-15  7:48                 ` [PATCH v3 1/3] common/xfs: Check if write supports [-c|-d] option in xfs_db xiao yang
2018-01-15  7:48                   ` [PATCH v3 2/3] common/filter: factor out expected XFS warnings for mount xiao yang
2018-01-15  7:48                   ` [PATCH v3 3/3] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-15 12:45               ` [PATCH v2 2/2] " Brian Foster
2018-01-15 21:03                 ` Dave Chinner
2018-01-16  4:02                   ` Eryu Guan
2018-01-16  6:41                     ` Xiao Yang
2018-01-16  7:26                     ` [PATCH v4 1/3] common/xfs: Check if write supports [-c|-d] option in xfs_db xiao yang
2018-01-16  7:26                       ` [PATCH v4 2/3] common/filter: factor out expected XFS warnings for mount xiao yang
2018-01-18  8:48                         ` Eryu Guan
2018-01-18  8:56                           ` Xiao Yang
2018-01-16  7:26                       ` [PATCH v4 3/3] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-18  8:46                         ` Eryu Guan
2018-01-18 10:49                           ` [PATCH v5 1/3] common/xfs: Check if write supports [-c|-d] option in xfs_db xiao yang
2018-01-18 10:49                             ` [PATCH v5 2/3] common/filter: Factor out expected XFS warnings for assert xiao yang
2018-01-18 18:29                               ` Darrick J. Wong
2018-01-19  2:51                                 ` Eryu Guan
2018-01-19  4:04                                 ` Xiao Yang
2018-01-19  5:38                                 ` [PATCH v6 2/3] common: Add _require_no_xfs_bug_on_assert && Factor out filter_xfs_dmesg xiao yang
2018-01-19  5:38                                   ` [PATCH v6 3/3] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-18 10:49                             ` [PATCH v5 " xiao yang
2018-01-18 18:19                             ` [PATCH v5 1/3] common/xfs: Check if write supports [-c|-d] option in xfs_db Darrick J. Wong
2018-01-16  8:50                     ` [PATCH v2 2/2] xfs: Regression test for invalid sb_logsunit Dave Chinner
2018-01-16 14:09                       ` Brian Foster
2018-01-18  8:44                         ` Eryu Guan
2018-01-16 13:58                   ` Brian Foster
2018-01-12  7:44     ` [PATCH v2 1/2] common/xfs: Check if write supports [-c|-d] option in xfs_db Eryu Guan
2018-01-12 16:43     ` Darrick J. Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5A58165B.9010706@cn.fujitsu.com \
    --to=yangx.jy@cn.fujitsu.com \
    --cc=darrick.wong@oracle.com \
    --cc=fstests@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox