Re: [PATCH v1 2/2] fa_notify_init(2): Support for FA_ flags has been backported to LTS kernels

[Amir Goldstein <amir73il@xxxxxxxxx>]

On Fri, Jul 12, 2024 at 8:57 PM <cel@xxxxxxxxxx> wrote:
>
> From: Chuck Lever <chuck.lever@xxxxxxxxxx>
>
> Signed-off-by: Chuck Lever <chuck.lever@xxxxxxxxxx>

Please fix typo in syscall name in title

> ---
>  man/man2/fanotify_init.2 | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>       Since Linux 5.13, the following interfaces can be used to control the amount of kernel resources consumed by fanotify:

> diff --git a/man/man2/fanotify_init.2 b/man/man2/fanotify_init.2
> index e5f9cbf298ee..51c7d61fd86d 100644
> --- a/man/man2/fanotify_init.2
> +++ b/man/man2/fanotify_init.2
> @@ -295,7 +295,7 @@ for additional details.
>  This is a synonym for
>  .RB ( FAN_REPORT_DIR_FID | FAN_REPORT_NAME ).
>  .TP
> -.BR FAN_REPORT_TARGET_FID " (since Linux 5.17)"
> +.BR FAN_REPORT_TARGET_FID " (since Linux 5.17, 5.15.154, and 5.10.220)"
>  .\" commit d61fd650e9d206a71fda789f02a1ced4b19944c4
>  Events for fanotify groups initialized with this flag
>  will contain additional information about the child
> --

I think that is also needed for
       FAN_REPORT_PIDFD (since Linux 5.15)
that was backported to 5.10.y?

There's also:
VERSIONS
       Prior to Linux 5.13, calling fanotify_init() required the
CAP_SYS_ADMIN capability.
       Since Linux 5.13, users may call fanotify_init() without the
CAP_SYS_ADMIN capability
       to create  and  initialize an fanotify group with limited functionality.

and in fanotify.7 there is:
       Since Linux 5.13, the following interfaces can be used to
control the amount
       of kernel resources consumed by fanotify...

Both these changes from 5.13 were backported to 5.10.y.

Thanks,
Amir.