Thread (16 messages) 16 messages, 3 authors, 2023-04-20

Re: [RFC][PATCH 1/2] fanotify: add support for FAN_UNMOUNT event

From: Christian Brauner <brauner@kernel.org>
Date: 2023-04-18 13:43:18
Also in: linux-fsdevel

On Fri, Apr 14, 2023 at 09:29:02PM +0300, Amir Goldstein wrote:
inotify generates unsolicited IN_UNMOUNT events for every inode
mark before the filesystem containing the inode is shutdown.

Unlike IN_UNMOUNT, FAN_UNMOUNT is an opt-in event that can only be
set on a mount mark and is generated when the mount is unmounted.

FAN_UNMOUNT requires FAN_REPORT_FID and reports an fid info record
with fsid of the filesystem and an empty file handle.

Signed-off-by: Amir Goldstein <amir73il@gmail.com>
---
I think this is a useful addition to the fanotify api and more useful
than IN_UMOUNT.

Going back to your cover letter. Afaiu, IN_UMOUNT is generated when the
superblock in which a watched object resides goes away. That's roughly
what I had in mind with FAN_SB_SHUTDOWN (ignoring naming discusions for
now).
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help