Hi Amir,

On 11/20/21 18:12, Amir Goldstein wrote:

Hi Alejandro,

This is a re-post of updates for v5.13 that I posted last March [1].

Thanks,
Amir.

Changes since v1:
- Update comment regarding tmpfs
- Document kernel commits

[1] https://lore.kernel.org/linux-man/20210318160817.3586288-1-amir73il@gmail.com/ (local)

Amir Goldstein (3):
   fanotify_init.2, fanotify_mark.2, fanotify.7: Configurable limits
   fanotify_mark.2: Update w.r.t tmpfs support
   fanotify_init.2: Document kernel commits

Matthew Bobrowski (1):
   fanotify_init.2, fanotify_mark.2: Document unprivileged listener

Patch set applied.
See some tweaks below.

Thanks!
Alex

---
     fanotify_init.2: Minor tweaks to Matthew's patch

     Signed-off-by: Alejandro Colomar [off-list ref]
     Cc: Matthew Bobrowski [off-list ref]
     Cc: Amir Goldstein [off-list ref]

diff --git a/man2/fanotify_init.2 b/man2/fanotify_init.2
index 7a1c21037..e463372f3 100644
--- a/man2/fanotify_init.2
+++ b/man2/fanotify_init.2

@@ -426,23 +426,23 @@ The user cannot request for an unlimited number of 

marks by using
  .BR FAN_UNLIMITED_MARKS .
  .IP * 3
  The user cannot request to use either notification classes
-.BR FAN_CLASS_CONTENT
+.B FAN_CLASS_CONTENT
  or
  .BR FAN_CLASS_PRE_CONTENT .
  This means that user cannot request permission events.
  .IP * 3
  The user is required to create a group that identifies filesystem 
objects by
  file handles, for example, by providing the
-.BR FAN_REPORT_FID
+.B FAN_REPORT_FID
  flag.
  .IP * 3
  The user is limited to only mark inodes.
  The ability to mark a mount or filesystem via
-.BR fanotify_mark()
+.BR fanotify_mark ()
  through the use of
-.BR FAN_MARK_MOUNT
+.B FAN_MARK_MOUNT
  or
-.BR FAN_MARK_FILESYSTEM
+.B FAN_MARK_FILESYSTEM
  is not permitted.
  .IP * 3
  The event object in the event queue is limited in terms of the information


-- 
Alejandro Colomar
Linux man-pages comaintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/