From: Edvard Conrad via ltp <ltp@lists.linux.it>
To: "ltp@lists.linux.it" <ltp@lists.linux.it>
Cc: Amir Goldstein <amir73il@gmail.com>, Jan Kara <jack@suse.cz>,
Edvard Conrad <edvard@tuta.io>
Subject: [LTP] [PATCH] syscalls/fanotify26: Move from staging to syscalls
Date: Sat, 31 Oct 2026 18:31:21 +0100 (CET) [thread overview]
Message-ID: <P5I00QE--F-9@tuta.io> (raw)
The kernel fix the second test case needs, commit c3d355f427ce ("fs:
let backing files inherit FMODE_NONOTIFY from the user file"), was
merged into Linus' tree on 2026-10-30 and will appear in v7.4-rc1.
Move the test out of runtest/staging, and record the fix in a
linux-git tag so that a failure points at the missing kernel commit
rather than at the test.
Signed-off-by: Edvard Conrad <edvard@tuta.io>
---
The follow-up Petr asked for on the fanotify26 thread:
https://lore.kernel.org/ltp/20261030110233.GA66190@pevik/
The fix is in Linus' tree as of 2026-10-30, but v7.4-rc1 is not tagged
yet, so if you would rather hold this until the rc is out, please do.
Kernel commit:
https://git.kernel.org/torvalds/c/c3d355f427cea70fbe31b49e21f1915dbf37f2e6
Both test cases pass on a kernel carrying the fix, and the second one
fails without it; that is unchanged by this patch, which only moves the
runtest entry and adds the tag.
runtest/staging | 1 -
runtest/syscalls | 1 +
testcases/kernel/syscalls/fanotify/fanotify26.c | 4 ++++
3 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/runtest/staging b/runtest/staging
index 2ce76b119..ef1cdea15 100644
--- a/runtest/staging
+++ b/runtest/staging
@@ -1,2 +1 @@
# Tests for features that are not yet in the stable kernel ABI
-fanotify26 fanotify26
diff --git a/runtest/syscalls b/runtest/syscalls
index ff3de1b15..23d3e21ef 100644
--- a/runtest/syscalls
+++ b/runtest/syscalls
@@ -703,6 +703,7 @@ fanotify22 fanotify22
fanotify23 fanotify23
fanotify24 fanotify24
fanotify25 fanotify25
+fanotify26 fanotify26
ioperm01 ioperm01
ioperm02 ioperm02
diff --git a/testcases/kernel/syscalls/fanotify/fanotify26.c b/testcases/kernel/syscalls/fanotify/fanotify26.c
index 8741cd560..63d7eea0f 100644
--- a/testcases/kernel/syscalls/fanotify/fanotify26.c
+++ b/testcases/kernel/syscalls/fanotify/fanotify26.c
@@ -192,6 +192,10 @@ static struct tst_test test = {
.mount_device = 1,
.needs_overlay = 1,
.mntpoint = OVL_BASE_MNTPOINT,
+ .tags = (const struct tst_tag[]) {
+ {"linux-git", "c3d355f427cea70fbe31b49e21f1915dbf37f2e6"},
+ {}
+ }
};
#else
--
2.56.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2026-10-31 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 17:31 Edvard Conrad via ltp [this message]
2026-10-31 19:37 ` [LTP] syscalls/fanotify26: Move from staging to syscalls linuxtestproject.agent
2026-11-01 16:46 ` [LTP] [PATCH] " Amir Goldstein
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=P5I00QE--F-9@tuta.io \
--to=ltp@lists.linux.it \
--cc=amir73il@gmail.com \
--cc=edvard@tuta.io \
--cc=jack@suse.cz \
/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.