From: Alejandro Colomar <alx@kernel.org>
To: Amir Goldstein <amir73il@gmail.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: Jann Horn <jannh@google.com>, Jan Kara <jack@suse.cz>,
Matthew Bobrowski <repnop@google.com>,
linux-man@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] man/man2/fanotify_mark.2: AT_FDCWD plus NULL path doesn't work
Date: Tue, 2 Jun 2026 00:19:39 +0200 [thread overview]
Message-ID: <ah4FXUpcE-6xlcDs@devuan> (raw)
In-Reply-To: <ahoIuOuC7q5M24dV@devuan>
[-- Attachment #1: Type: text/plain, Size: 2158 bytes --]
Hi,
On 2026-05-29T23:45:55+0200, Alejandro Colomar wrote:
> Hi Jann, Amir,
>
> On 2026-05-29T23:38:11+0200, Amir Goldstein wrote:
> > On Fri, May 29, 2026 at 7:27 PM Jann Horn <jannh@google.com> wrote:
> > >
> > > The fanotify_mark.2 manpage claims that AT_FDCWD works with a NULL path,
> > > but there is no kernel code for that - in fanotify_find_path(), in the
> > > `if (filename == NULL)` block, the fd is only used for a normal FD
> > > lookup.
> > >
> > > This was also already the case when this manpage was written back in
> > > 2014, so remove the bogus documentation.
> > >
> > > Fixes: c200b422d ("fanotify_mark.2: New page documenting fanotify_mark(2)")
> > > Signed-off-by: Jann Horn <jannh@google.com>
> >
> > Hah, never noticed this.
> > Apparently, hallucinations already existed in 2014 :D
> >
> > Acked-by: Amir Goldstein <amir73il@gmail.com>
>
> Thanks! I've added the author of the fixed commit in the recipients.
> I'll apply on Monday or so.
I've applied the patch and tag now. Thanks!
Have a lovely night!
Alex
>
>
> Have a lovely night!
> Alex
>
> >
> > > ---
> > > man/man2/fanotify_mark.2 | 8 --------
> > > 1 file changed, 8 deletions(-)
> > >
> > > diff --git a/man/man2/fanotify_mark.2 b/man/man2/fanotify_mark.2
> > > index e561ffd21..a3b77537c 100644
> > > --- a/man/man2/fanotify_mark.2
> > > +++ b/man/man2/fanotify_mark.2
> > > @@ -560,14 +560,6 @@ defines the filesystem object to be marked.
> > > .IP \[bu]
> > > If
> > > .I path
> > > -is NULL, and
> > > -.I dirfd
> > > -takes the special value
> > > -.BR AT_FDCWD ,
> > > -the current working directory is to be marked.
> > > -.IP \[bu]
> > > -If
> > > -.I path
> > > is absolute, it defines the filesystem object to be marked, and
> > > .I dirfd
> > > is ignored.
> > >
> > > ---
> > > base-commit: 9db8ca91f920b9aba40ed68de6b8da0ca9dbefaa
> > > change-id: 20260529-fan-mark-cwd-1c760106eff9
> > >
> > > Best regards,
> > > --
> > > Jann Horn <jannh@google.com>
> > >
> >
>
> --
> <https://www.alejandro-colomar.es>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-06-01 22:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 17:27 [PATCH] man/man2/fanotify_mark.2: AT_FDCWD plus NULL path doesn't work Jann Horn
2026-05-29 21:38 ` Amir Goldstein
2026-05-29 21:45 ` Alejandro Colomar
2026-06-01 22:19 ` Alejandro Colomar [this message]
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=ah4FXUpcE-6xlcDs@devuan \
--to=alx@kernel.org \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=repnop@google.com \
--cc=xypron.glpk@gmx.de \
/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