From: Chao Yu <chao@kernel.org>
To: Zorro Lang <zlang@kernel.org>, fstests@vger.kernel.org
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
Chao Yu <chao@kernel.org>
Subject: [PATCH] common/rc: support f2fs in _require_fanotify_ioerrors()
Date: Tue, 24 Mar 2026 10:56:55 +0800 [thread overview]
Message-ID: <20260324025656.493776-1-chao@kernel.org> (raw)
This patch allows to run generic/791 on f2fs.
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 5fe44e21..8f09f19a 100644
--- a/common/rc
+++ b/common/rc
@@ -6184,6 +6184,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
esac
_notrun "$FSTYP does not support fanotify ioerrors"
--
2.49.0
next reply other threads:[~2026-03-24 2:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 2:56 Chao Yu [this message]
2026-03-25 5:53 ` [PATCH] common/rc: support f2fs in _require_fanotify_ioerrors() Christoph Hellwig
2026-03-25 6:30 ` Chao Yu
2026-03-31 20:11 ` Zorro Lang
2026-04-01 6:19 ` Christoph Hellwig
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=20260324025656.493776-1-chao@kernel.org \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox