From: Zorro Lang <zlang@kernel.org>
To: Anand Jain <asj@kernel.org>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, djwong@kernel.org
Subject: Re: [PATCH v8 04/13] fstests: add _require_fanotify_function
Date: Tue, 1 Sep 2026 23:42:44 +0800 [thread overview]
Message-ID: <apbxt_WcZOYfmfd9@zlang-mailbox> (raw)
In-Reply-To: <d8fb7f5c0d67cf01249e8fc4807e963cc1a353d0.1784949155.git.asj@kernel.org>
On Sat, Jul 25, 2026 at 03:39:01PM +0800, Anand Jain wrote:
> fanotify support may not be compiled into the kernel. Add
> _require_fanotify_function to skip tests when fanotify is disabled.
>
> Signed-off-by: Anand Jain <asj@kernel.org>
> ---
> common/rc | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/common/rc b/common/rc
> index 53e5d9d43af6..21b516accdf7 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -6329,6 +6329,13 @@ _require_max_file_range_blocks()
> esac
> }
>
> +_require_fanotify_function()
> +{
> + if $FSNOTIFYWAIT_PROG 2>&1 | grep -q "Function not implemented"; then
> + _notrun "Need CONFIG_FANOTIFY and CONFIG_FANOTIFY_ACCESS_PERMISSIONS to be enabled"
> + fi
What happens if $FSNOTIFYWAIT_PROG fails with an error other than
'Function not implemented'?
Thanks,
Zorro
> +}
> +
> _require_fanotify_ioerrors()
> {
> local x
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-09-01 15:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 7:38 [PATCH v8 0/13] fstests: add test coverage for cloned filesystem ids Anand Jain
2026-07-25 7:38 ` [PATCH v8 01/13] fstests: add _loop_image_create_clone() helper Anand Jain
2026-09-01 12:33 ` Zorro Lang
2026-09-01 13:52 ` Anand Suveer Jain
2026-07-25 7:38 ` [PATCH v8 02/13] fstests: add _clone_mount_option() helper Anand Jain
2026-09-01 12:39 ` Zorro Lang
2026-09-01 13:54 ` Anand Suveer Jain
2026-07-25 7:39 ` [PATCH v8 03/13] fstests: add FSNOTIFYWAIT_PROG Anand Jain
2026-09-01 15:37 ` Zorro Lang
2026-07-25 7:39 ` [PATCH v8 04/13] fstests: add _require_fanotify_function Anand Jain
2026-09-01 15:42 ` Zorro Lang [this message]
2026-07-25 7:39 ` [PATCH v8 05/13] fstests: add _require_unique_f_fsid() helper Anand Jain
2026-09-01 16:09 ` Zorro Lang
2026-07-25 7:39 ` [PATCH v8 06/13] fstests: add SEMANAGE_PROG Anand Jain
2026-07-25 7:39 ` [PATCH v8 07/13] fstests: verify fanotify isolation on cloned filesystems Anand Jain
2026-07-25 7:39 ` [PATCH v8 08/13] fstests: verify f_fsid for " Anand Jain
2026-07-25 7:39 ` [PATCH v8 09/13] fstests: verify libblkid resolution of duplicate UUIDs Anand Jain
2026-07-25 7:39 ` [PATCH v8 10/13] fstests: verify IMA isolation on cloned filesystems Anand Jain
2026-07-25 7:39 ` [PATCH v8 11/13] fstests: verify exportfs file handles " Anand Jain
2026-07-25 7:39 ` [PATCH v8 12/13] fstests: add _change_metadata_uuid helper Anand Jain
2026-07-25 7:39 ` [PATCH v8 13/13] fstests: test UUID consistency for clones with metadata_uuid Anand Jain
2026-08-31 7:17 ` [PATCH v8 0/13] fstests: add test coverage for cloned filesystem ids 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=apbxt_WcZOYfmfd9@zlang-mailbox \
--to=zlang@kernel.org \
--cc=asj@kernel.org \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-xfs@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