[LTP] [PATCH 0/5] LTP fanotify tests for v6.13

[Amir Goldstein]

On Wed, Jan 22, 2025 at 9:50 PM Petr Vorel <pvorel@suse.cz> wrote:
>
> Hi Amir,
>
> > Hi all,
>
> > Following tests for fanotify code in v6.13.
>
> > 1. The new test case in fanotify13 fails as follows on kernels v6.6..v6.12:
>
> > fanotify13.c:282: TFAIL: handle_bytes (0) returned in event does not equal to handle_bytes (24) returned in name_to_handle_at(2)
> > fanotify13.c:282: TFAIL: handle_bytes (0) returned in event does not equal to handle_bytes (24) returned in name_to_handle_at(2)
> > fanotify13.c:282: TFAIL: handle_bytes (180003) returned in event does not equal to handle_bytes (24) returned in name_to_handle_at(2)
>
> > The fix was already backported to v6.12.10.
> > It was also backported to v6.6.72,
> > but then reverted due to a backport bug in v6.6.73
> > and it now staged again for v6.6.74.
>
>
> > 2. The new variant of fanotify21 is skipped on kernels <= v6.12
>
> > This variant tests the new feature flag FAN_REPORT_FD_ERROR, which is
> > not effectively a bug fix.
>
> > Because this feature was added as a consequence of a bug report,
> > it was auto backported to v6.12.5 and to v6.6.66, but I do not
> > feel comfortable with adding a fix tag to force distros to backport
> > this feature.
>
> We have git freeze before new release. But IMHO this should go in.
> It works well on v6.13, I'll retest it on SLES kernels.
>

OK. For the record, I try to time the posting of these sorts of tests
after the .0 kernel release.

Arguably, I could have posted the fanotify13 test case after the release
of v6.13-rc7 a week earlier, but I often need  more time to context switch
for posting the tests.

Are the LTP releases usually timed in some relation to .0 release times?

Thanks,
Amir.