From: Chao Yu <chao@kernel.org>
To: Anand Suveer Jain <asj@kernel.org>, Zorro Lang <zlang@kernel.org>,
fstests@vger.kernel.org
Cc: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
"Darrick J. Wong" <djwong@kernel.org>
Subject: Re: [PATCH v2] common/rc: support f2fs in _require_fanotify_ioerrors()
Date: Wed, 8 Jul 2026 11:25:37 +0800 [thread overview]
Message-ID: <5c11cd98-bb41-46e0-9765-e2aad57a08e4@kernel.org> (raw)
In-Reply-To: <af5f0eb1-0197-4952-a37b-0602799929ec@kernel.org>
On 7/7/26 18:13, Anand Suveer Jain wrote:
> On 6/7/26 14:43, Chao Yu wrote:
>> f2fs has supported to report fserror, this patch adds support for f2fs
>> in _require_fanotify_ioerrors(), so that we can run generic/791 on f2fs.
>>
>> Cc: Darrick J. Wong <djwong@kernel.org>
>> Signed-off-by: Chao Yu <chao@kernel.org>
>> ---
>> common/rc | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/common/rc b/common/rc
>> index 494725547..f51ad59f3 100644
>> --- a/common/rc
>> +++ b/common/rc
>> @@ -6257,6 +6257,9 @@ _require_fanotify_ioerrors()
>> x="$(_get_fs_sysfs_attr $TEST_DEV err_report_sec)"
>> test -n "$x" && return 0
>> ;;
>
>
>> + f2fs)
>> + x="$(cat /sys/fs/f2fs/features/fserror)"
>> + test -n "$x" && return 0
>
> Don't we need to check if /sys/fs/f2fs/features/fserror
> is present in the running kernel (there are helpers)
Hi Anand,
You mean _has_fs_sysfs_attr()? however, it forces to check first parameter $dev
w/ block device type:
if [ ! -b "$dev" -o -z "$attr" ];then
_fail "Usage: _has_fs_sysfs_attr <mounted_device> <attr>"
fi
> before reading it?
How about this?
f2fs)
local feat_file="/sys/fs/f2fs/features/fserror"
if [ -f "$feat_file" ] && [ "$(cat "$feat_file")" = "supported" ]; then
return 0
fi
;;
>
>
>
>> esac
>>
>> _notrun "$FSTYP does not support fanotify ioerrors"
>
next prev parent reply other threads:[~2026-07-08 3:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 6:43 [PATCH v2] common/rc: support f2fs in _require_fanotify_ioerrors() Chao Yu
2026-07-07 10:13 ` Anand Suveer Jain
2026-07-08 3:25 ` Chao Yu [this message]
2026-07-08 6:03 ` Anand Suveer Jain
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=5c11cd98-bb41-46e0-9765-e2aad57a08e4@kernel.org \
--to=chao@kernel.org \
--cc=asj@kernel.org \
--cc=djwong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox