All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Chao Yu <chao@kernel.org>
Cc: Zorro Lang <zlang@kernel.org>,
	fstests@vger.kernel.org, jaegeuk@kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH v4 6/6] f2fs/009: detect and repair nlink corruption
Date: Tue, 25 Mar 2025 20:15:26 +1100	[thread overview]
Message-ID: <Z-J0LnCEWX2bo9LF@dread.disaster.area> (raw)
In-Reply-To: <20250312072309.3989074-6-chao@kernel.org>

On Wed, Mar 12, 2025 at 03:23:09PM +0800, Chao Yu wrote:
> This is a regression test to check whether fsck can handle corrupted
> nlinks correctly, it uses inject.f2fs to inject nlinks w/ wrong value,
> and expects fsck.f2fs can detect such corruption and do the repair.
> 
> Cc: Jaegeuk Kim <jaegeuk@kernel.org>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> v4:
> - remove unnecessary "_require_command fsck.f2fs"
> - clean up _fixed_by_git_commit line
> - fix to clean all tmp files in _cleanup
>  tests/f2fs/009     | 147 +++++++++++++++++++++++++++++++++++++++++++++
>  tests/f2fs/009.out |   2 +
>  2 files changed, 149 insertions(+)
>  create mode 100755 tests/f2fs/009
>  create mode 100644 tests/f2fs/009.out
> 
> diff --git a/tests/f2fs/009 b/tests/f2fs/009
> new file mode 100755
> index 00000000..9120d8a5
> --- /dev/null
> +++ b/tests/f2fs/009
> @@ -0,0 +1,147 @@
> +#! /bin/bash
> +# SPDX-License-Identifier: GPL-2.0
> +# Copyright (c) 2025 Chao Yu.  All Rights Reserved.
> +#
> +# FS QA Test No. f2fs/009
> +#
> +# This is a regression test to check whether fsck can handle corrupted
> +# nlinks correctly, it uses inject.f2fs to inject nlinks w/ wrong value,
> +# and expects fsck.f2fs can detect such corruption and do the repair.
> +#
> +. ./common/preamble
> +_begin_fstest auto quick
> +
> +if [ ! -x "$(type -P socket)" ]; then
> +	_notrun "Couldn't find socket"
> +fi
> +
> +_require_scratch
> +_require_command "$F2FS_INJECT_PROG" inject.f2fs
> +
> +_fixed_by_git_commit f2fs-tools 958cd6e \
> +	"fsck.f2fs: support to repair corrupted i_links"
> +
> +filename=$SCRATCH_MNT/foo
> +hardlink=$SCRATCH_MNT/bar
> +
> +_cleanup()
> +{
> +	if [ -n "$pid" ]; then
> +		kill $pid &> /dev/null
> +		wait
> +	fi
> +	cd /
> +	rm -r -f $tmp.*
> +}
> +
> +for ((i=0;i<14;i++)) do
> +	echo "round: " $i >> $seqres.full
> +
> +	_scratch_mkfs >> $seqres.full
> +	_scratch_mount
> +
> +	if [ $i == 0 ]; then
> +		touch $filename
> +		ino=`stat -c '%i' $filename`
> +		nlink=0
> +	elif [ $i == 1 ]; then
.....

Ok, it works, but it's a bit nasty. You want to run the same
injection and checking on all types of inodes, so factor that out
like so:

inject_and_check()
{
	local nlink=$1
	local ino=`stat -c '%i' $filename`

	echo "ino:"$ino >> $seqres.full
	echo "nlink:"$nlink >> $seqres.full

	_scratch_unmount

	$F2FS_INJECT_PROG --node --mb i_links --nid $ino --val $nlink $SCRATCH_DEV \
		>> $seqres.full || _fail "fail to inject"

	_check_scratch_fs >> $seqres.full 2>&1 && _fail "can't find corruption"
	_repair_scratch_fs >> $seqres.full
	_check_scratch_fs >> $seqres.full 2>&1 || _fail "fsck can't fix corruption"

	_scratch_mount
	_scratch_unmount

	_scratch_mkfs >> $seqres.full
	_scratch_mount
}

And now most of the test cases become this:

_scratch_mkfs >> $seqres.full
_scratch_mount

touch $filename
inject_and_check 0

mkdir $filename
inject_and_check 1

mknod $filename c 9 0
inject_and_check 0

mknod $filename b 8 0
inject_and_check 0

.....

The whacky cases with socket and orphan inodes can be handled
by factoring inject_and_check so there's a second function that
takes both ino and nlink as parameters.

This gets rid of all the unnecessary if/elif logic and looping, 
leaving only the test code that does the work behind.

-Dave.
-- 
Dave Chinner
david@fromorbit.com

WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, Zorro Lang <zlang@kernel.org>,
	fstests@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v4 6/6] f2fs/009: detect and repair nlink corruption
Date: Tue, 25 Mar 2025 20:15:26 +1100	[thread overview]
Message-ID: <Z-J0LnCEWX2bo9LF@dread.disaster.area> (raw)
In-Reply-To: <20250312072309.3989074-6-chao@kernel.org>

On Wed, Mar 12, 2025 at 03:23:09PM +0800, Chao Yu wrote:
> This is a regression test to check whether fsck can handle corrupted
> nlinks correctly, it uses inject.f2fs to inject nlinks w/ wrong value,
> and expects fsck.f2fs can detect such corruption and do the repair.
> 
> Cc: Jaegeuk Kim <jaegeuk@kernel.org>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> v4:
> - remove unnecessary "_require_command fsck.f2fs"
> - clean up _fixed_by_git_commit line
> - fix to clean all tmp files in _cleanup
>  tests/f2fs/009     | 147 +++++++++++++++++++++++++++++++++++++++++++++
>  tests/f2fs/009.out |   2 +
>  2 files changed, 149 insertions(+)
>  create mode 100755 tests/f2fs/009
>  create mode 100644 tests/f2fs/009.out
> 
> diff --git a/tests/f2fs/009 b/tests/f2fs/009
> new file mode 100755
> index 00000000..9120d8a5
> --- /dev/null
> +++ b/tests/f2fs/009
> @@ -0,0 +1,147 @@
> +#! /bin/bash
> +# SPDX-License-Identifier: GPL-2.0
> +# Copyright (c) 2025 Chao Yu.  All Rights Reserved.
> +#
> +# FS QA Test No. f2fs/009
> +#
> +# This is a regression test to check whether fsck can handle corrupted
> +# nlinks correctly, it uses inject.f2fs to inject nlinks w/ wrong value,
> +# and expects fsck.f2fs can detect such corruption and do the repair.
> +#
> +. ./common/preamble
> +_begin_fstest auto quick
> +
> +if [ ! -x "$(type -P socket)" ]; then
> +	_notrun "Couldn't find socket"
> +fi
> +
> +_require_scratch
> +_require_command "$F2FS_INJECT_PROG" inject.f2fs
> +
> +_fixed_by_git_commit f2fs-tools 958cd6e \
> +	"fsck.f2fs: support to repair corrupted i_links"
> +
> +filename=$SCRATCH_MNT/foo
> +hardlink=$SCRATCH_MNT/bar
> +
> +_cleanup()
> +{
> +	if [ -n "$pid" ]; then
> +		kill $pid &> /dev/null
> +		wait
> +	fi
> +	cd /
> +	rm -r -f $tmp.*
> +}
> +
> +for ((i=0;i<14;i++)) do
> +	echo "round: " $i >> $seqres.full
> +
> +	_scratch_mkfs >> $seqres.full
> +	_scratch_mount
> +
> +	if [ $i == 0 ]; then
> +		touch $filename
> +		ino=`stat -c '%i' $filename`
> +		nlink=0
> +	elif [ $i == 1 ]; then
.....

Ok, it works, but it's a bit nasty. You want to run the same
injection and checking on all types of inodes, so factor that out
like so:

inject_and_check()
{
	local nlink=$1
	local ino=`stat -c '%i' $filename`

	echo "ino:"$ino >> $seqres.full
	echo "nlink:"$nlink >> $seqres.full

	_scratch_unmount

	$F2FS_INJECT_PROG --node --mb i_links --nid $ino --val $nlink $SCRATCH_DEV \
		>> $seqres.full || _fail "fail to inject"

	_check_scratch_fs >> $seqres.full 2>&1 && _fail "can't find corruption"
	_repair_scratch_fs >> $seqres.full
	_check_scratch_fs >> $seqres.full 2>&1 || _fail "fsck can't fix corruption"

	_scratch_mount
	_scratch_unmount

	_scratch_mkfs >> $seqres.full
	_scratch_mount
}

And now most of the test cases become this:

_scratch_mkfs >> $seqres.full
_scratch_mount

touch $filename
inject_and_check 0

mkdir $filename
inject_and_check 1

mknod $filename c 9 0
inject_and_check 0

mknod $filename b 8 0
inject_and_check 0

.....

The whacky cases with socket and orphan inodes can be handled
by factoring inject_and_check so there's a second function that
takes both ino and nlink as parameters.

This gets rid of all the unnecessary if/elif logic and looping, 
leaving only the test code that does the work behind.

-Dave.
-- 
Dave Chinner
david@fromorbit.com


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  parent reply	other threads:[~2025-03-25  9:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12  7:23 [PATCH v4 1/6] common/config: remove redundant export variables Chao Yu
2025-03-12  7:23 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-03-12  7:23 ` [PATCH v4 2/6] common/config: export F2FS_INJECT_PROG Chao Yu
2025-03-12  7:23   ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-03-12  7:23 ` [PATCH v4 3/6] common/config: export F2FS_FSCK_PROG Chao Yu
2025-03-12  7:23   ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-03-12  7:23 ` [PATCH v4 4/6] common/rc: use -f for mkfs.f2fs by default Chao Yu
2025-03-12  7:23   ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-03-12  7:23 ` [PATCH v4 5/6] common/rc: introduce _check_f2fs_filesystem() Chao Yu
2025-03-12  7:23   ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-03-12  7:23 ` [PATCH v4 6/6] f2fs/009: detect and repair nlink corruption Chao Yu
2025-03-12  7:23   ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-03-25  1:07   ` Zorro Lang
2025-03-25  1:07     ` [f2fs-dev] " Zorro Lang via Linux-f2fs-devel
2025-03-25  6:54     ` Chao Yu
2025-03-25  6:54       ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-03-25  9:15   ` Dave Chinner [this message]
2025-03-25  9:15     ` Dave Chinner via Linux-f2fs-devel
2025-03-25 12:55     ` Chao Yu
2025-03-25 12:55       ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel

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=Z-J0LnCEWX2bo9LF@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=chao@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=zlang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.