[LTP] [PATCH] syscalls/fanotify26: Move from staging to syscalls

[Amir Goldstein]

On Sat, Oct 31, 2026 at 6:31 PM Edvard Conrad <edvard@tuta.io> wrote:
>
> 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.

Not only is rc1 not out yet, but we already have a report on
the dir open bug for which you have added another test case.
So I think it is best wait for the other bug fix to land, hopefully
sometime next week before moving the test out of staging.

On the other hand, Petr, this is not a new feature, it is a real bug fix.
Are we holding off on running tests on newly found bugs
until those bugs are fixed upstream?

Hopefully there is not going to be a large time gap between
bug report and bug fix, so it does not matter much.
I was just wondering about best practice.

Thanks,
Amir.