public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>, Jan Kara <jack@suse.cz>,
	Matthew Bobrowski <repnop@google.com>,
	linux-man@vger.kernel.org
Subject: [PATCH v3 0/2] fanotify man page updates for v5.17
Date: Thu, 30 Jun 2022 22:06:08 +0300	[thread overview]
Message-ID: <20220630190610.3043428-1-amir73il@gmail.com> (raw)

Hi Alex,

These two complementary APIs, FAN_REPORT_TARGET_FID (fanotify_init)
and FAN_RENAME (fanotify_mark) were merged to kernel v5.17.

Note that we used the fact that this is new API to fix a glitch that
exists in the old APIs - it is possble to request CREATE/DELETE/MOVE
events and flags FAN_ONDIR/FAN_EVENT_ON_CHILD for a non-directrory,
but those events and flags are only relevant for directories.

When the new APIs are used, ENOTDIR will be returned in such cases
and this change is reflected in the man pages updates.

The ENOTDIR error was added by later commits, one of them just merged
to mainline, which are also mentioned in the commit message of the
first patch.

Both Jan and Matthew re-reviewed the changes to the ENOTDIR section.

Thanks,
Amir,

Changes since v2:
- Rearrange ENOTDIR errors section
- Add more cases of ENOTDIR following fix patch

Amir Goldstein (2):
  fanotify.7, fanotify_init.2: Document FAN_REPORT_TARGET_FID
  fanotify.7, fanotify_init.2, fanotify_mark.2: Document FAN_RENAME

 man2/fanotify_init.2 | 55 ++++++++++++++++++++++++++++++++++++++++----
 man2/fanotify_mark.2 | 41 +++++++++++++++++++++++++++++++++
 man7/fanotify.7      | 31 ++++++++++++++-----------
 3 files changed, 109 insertions(+), 18 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-06-30 19:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 19:06 Amir Goldstein [this message]
2022-06-30 19:06 ` [PATCH v3 1/2] fanotify.7, fanotify_init.2: Document FAN_REPORT_TARGET_FID Amir Goldstein
2022-07-03 19:24   ` Alejandro Colomar
     [not found]     ` <CAOQ4uxjMDq9nb0hBSV_Fbf190GdwLfTd2+erY9+KTnw4NmBo7Q@mail.gmail.com>
2022-07-04  9:55       ` Alejandro Colomar
2022-06-30 19:06 ` [PATCH v3 2/2] fanotify.7, fanotify_init.2, fanotify_mark.2: Document FAN_RENAME 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=20220630190610.3043428-1-amir73il@gmail.com \
    --to=amir73il@gmail.com \
    --cc=alx.manpages@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=repnop@google.com \
    /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