From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Zorro Lang <zlang@kernel.org>, fstests@vger.kernel.org
Cc: jaegeuk@kernel.org, "Darrick J. Wong" <djwong@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH v2] common/rc: support f2fs in _require_fanotify_ioerrors()
Date: Mon, 6 Jul 2026 06:43:26 +0000 [thread overview]
Message-ID: <20260706064326.3657995-1-chao@kernel.org> (raw)
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
esac
_notrun "$FSTYP does not support fanotify ioerrors"
--
2.49.0
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
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>, "Darrick J. Wong" <djwong@kernel.org>
Subject: [PATCH v2] common/rc: support f2fs in _require_fanotify_ioerrors()
Date: Mon, 6 Jul 2026 06:43:26 +0000 [thread overview]
Message-ID: <20260706064326.3657995-1-chao@kernel.org> (raw)
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
esac
_notrun "$FSTYP does not support fanotify ioerrors"
--
2.49.0
next reply other threads:[~2026-07-06 6:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 6:43 Chao Yu via Linux-f2fs-devel [this message]
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-07 10:13 ` [f2fs-dev] " Anand Suveer Jain via Linux-f2fs-devel
2026-07-08 3:25 ` Chao Yu
2026-07-08 3:25 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-07-08 6:03 ` Anand Suveer Jain
2026-07-08 6:03 ` [f2fs-dev] " Anand Suveer Jain 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=20260706064326.3657995-1-chao@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--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.