From: Jan Kara <jack@suse.cz> To: Amir Goldstein <amir73il@gmail.com> Cc: Jan Kara <jack@suse.cz>, linux-fsdevel@vger.kernel.org Subject: Re: [PATCH v5 17/22] fsnotify: send MOVE_SELF event with parent/name info Date: Thu, 16 Jul 2020 15:45:56 +0200 [thread overview] Message-ID: <20200716134556.GE5022@quack2.suse.cz> (raw) In-Reply-To: <20200716084230.30611-18-amir73il@gmail.com> On Thu 16-07-20 11:42:25, Amir Goldstein wrote: > MOVE_SELF event does not get reported to a parent watching children > when a child is moved, but it can be reported to sb/mount mark or to > the moved inode itself with parent/name info if group is interested > in parent/name info. > > Use the fsnotify_parent() helper to send a MOVE_SELF event and adjust > fsnotify() to handle the case of an event "on child" that should not > be sent to the watching parent's inode mark. > > Signed-off-by: Amir Goldstein <amir73il@gmail.com> What I find strange about this is that the MOVE_SELF event will be reported to the new parent under the new name (just due to the way how dentry handling in vfs_rename() works). That seems rather arbitrary and I'm not sure it would be useful? I guess anybody needing dir info with renames will rather use FS_MOVED_FROM / FS_MOVED_TO where it is well defined? So can we leave FS_MOVE_SELF as one of those cases that doesn't report parent + name info? Honza > --- > fs/notify/fsnotify.c | 22 ++++++++++++++++++---- > include/linux/fsnotify.h | 4 +--- > include/linux/fsnotify_backend.h | 2 +- > 3 files changed, 20 insertions(+), 8 deletions(-) > > diff --git a/fs/notify/fsnotify.c b/fs/notify/fsnotify.c > index efa5c1c4908a..fa84aea47b20 100644 > --- a/fs/notify/fsnotify.c > +++ b/fs/notify/fsnotify.c > @@ -367,6 +367,7 @@ int fsnotify(struct inode *to_tell, __u32 mask, const void *data, int data_type, > struct super_block *sb = to_tell->i_sb; > struct inode *dir = S_ISDIR(to_tell->i_mode) ? to_tell : NULL; > struct mount *mnt = NULL; > + struct inode *inode = NULL; > struct inode *child = NULL; > int ret = 0; > __u32 test_mask, marks_mask; > @@ -377,6 +378,14 @@ int fsnotify(struct inode *to_tell, __u32 mask, const void *data, int data_type, > if (mask & FS_EVENT_ON_CHILD) > child = fsnotify_data_inode(data, data_type); > > + /* > + * If event is "on child" then to_tell is a watching parent. > + * An event "on child" may be sent to mount/sb mark with parent/name > + * info, but not appropriate for watching parent (e.g. FS_MOVE_SELF). > + */ > + if (!child || (mask & FS_EVENTS_POSS_ON_CHILD)) > + inode = to_tell; > + > /* > * Optimization: srcu_read_lock() has a memory barrier which can > * be expensive. It protects walking the *_fsnotify_marks lists. > @@ -384,14 +393,17 @@ int fsnotify(struct inode *to_tell, __u32 mask, const void *data, int data_type, > * SRCU because we have no references to any objects and do not > * need SRCU to keep them "alive". > */ > - if (!to_tell->i_fsnotify_marks && !sb->s_fsnotify_marks && > + if (!sb->s_fsnotify_marks && > (!mnt || !mnt->mnt_fsnotify_marks) && > + (!inode || !inode->i_fsnotify_marks) && > (!child || !child->i_fsnotify_marks)) > return 0; > > - marks_mask = to_tell->i_fsnotify_mask | sb->s_fsnotify_mask; > + marks_mask = sb->s_fsnotify_mask; > if (mnt) > marks_mask |= mnt->mnt_fsnotify_mask; > + if (inode) > + marks_mask |= inode->i_fsnotify_mask; > if (child) > marks_mask |= child->i_fsnotify_mask; > > @@ -406,14 +418,16 @@ int fsnotify(struct inode *to_tell, __u32 mask, const void *data, int data_type, > > iter_info.srcu_idx = srcu_read_lock(&fsnotify_mark_srcu); > > - iter_info.marks[FSNOTIFY_OBJ_TYPE_INODE] = > - fsnotify_first_mark(&to_tell->i_fsnotify_marks); > iter_info.marks[FSNOTIFY_OBJ_TYPE_SB] = > fsnotify_first_mark(&sb->s_fsnotify_marks); > if (mnt) { > iter_info.marks[FSNOTIFY_OBJ_TYPE_VFSMOUNT] = > fsnotify_first_mark(&mnt->mnt_fsnotify_marks); > } > + if (inode) { > + iter_info.marks[FSNOTIFY_OBJ_TYPE_INODE] = > + fsnotify_first_mark(&inode->i_fsnotify_marks); > + } > if (child) { > iter_info.marks[FSNOTIFY_OBJ_TYPE_CHILD] = > fsnotify_first_mark(&child->i_fsnotify_marks); > diff --git a/include/linux/fsnotify.h b/include/linux/fsnotify.h > index fe4f2bc5b4c2..61dccaf21e7b 100644 > --- a/include/linux/fsnotify.h > +++ b/include/linux/fsnotify.h > @@ -131,7 +131,6 @@ static inline void fsnotify_move(struct inode *old_dir, struct inode *new_dir, > u32 fs_cookie = fsnotify_get_cookie(); > __u32 old_dir_mask = FS_MOVED_FROM; > __u32 new_dir_mask = FS_MOVED_TO; > - __u32 mask = FS_MOVE_SELF; > const struct qstr *new_name = &moved->d_name; > > if (old_dir == new_dir) > @@ -140,7 +139,6 @@ static inline void fsnotify_move(struct inode *old_dir, struct inode *new_dir, > if (isdir) { > old_dir_mask |= FS_ISDIR; > new_dir_mask |= FS_ISDIR; > - mask |= FS_ISDIR; > } > > fsnotify_name(old_dir, old_dir_mask, source, old_name, fs_cookie); > @@ -149,7 +147,7 @@ static inline void fsnotify_move(struct inode *old_dir, struct inode *new_dir, > if (target) > fsnotify_link_count(target); > > - fsnotify(source, mask, source, FSNOTIFY_EVENT_INODE, NULL, 0); > + fsnotify_dentry(moved, FS_MOVE_SELF); > audit_inode_child(new_dir, moved, AUDIT_TYPE_CHILD_CREATE); > } > > diff --git a/include/linux/fsnotify_backend.h b/include/linux/fsnotify_backend.h > index 6f0df110e9f8..acce2ec17edf 100644 > --- a/include/linux/fsnotify_backend.h > +++ b/include/linux/fsnotify_backend.h > @@ -89,7 +89,7 @@ > * It may include events that can be sent to an inode/sb/mount mark, but cannot > * be sent to a parent watching children. > */ > -#define FS_EVENTS_POSS_TO_PARENT (FS_EVENTS_POSS_ON_CHILD) > +#define FS_EVENTS_POSS_TO_PARENT (FS_EVENTS_POSS_ON_CHILD | FS_MOVE_SELF) > > /* Events that can be reported to backends */ > #define ALL_FSNOTIFY_EVENTS (ALL_FSNOTIFY_DIRENT_EVENTS | \ > -- > 2.17.1 > -- Jan Kara <jack@suse.com> SUSE Labs, CR
next prev parent reply other threads:[~2020-07-16 13:45 UTC|newest] Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-16 8:42 [PATCH v5 00/22] fanotify events with name info Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 01/22] fanotify: generalize the handling of extra event flags Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 02/22] fanotify: generalize merge logic of events on dir Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 03/22] fanotify: distinguish between fid encode error and null fid Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 04/22] fanotify: generalize test for FAN_REPORT_FID Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 05/22] fanotify: mask out special event flags from ignored mask Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 06/22] fanotify: prepare for implicit event flags in mark mask Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 07/22] fanotify: use FAN_EVENT_ON_CHILD as implicit flag on sb/mount/non-dir marks Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 08/22] fsnotify: add object type "child" to object type iterator Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 09/22] fanotify: use struct fanotify_info to parcel the variable size buffer Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 10/22] fanotify: no external fh buffer in fanotify_name_event Amir Goldstein 2020-07-16 12:44 ` Jan Kara 2020-07-16 13:30 ` Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 11/22] dnotify: report both events on parent and child with single callback Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 12/22] inotify: " Amir Goldstein 2020-07-16 12:52 ` Jan Kara 2020-07-16 14:25 ` Amir Goldstein 2020-07-16 15:17 ` Jan Kara 2020-07-16 8:42 ` [PATCH v5 13/22] fanotify: " Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 14/22] fsnotify: send event to " Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 15/22] fsnotify: send event with parent/name info to sb/mount/non-dir marks Amir Goldstein 2020-07-16 17:01 ` Jan Kara 2020-07-16 17:20 ` Amir Goldstein 2020-07-16 17:57 ` Jan Kara 2020-07-16 18:42 ` Amir Goldstein 2020-07-16 22:34 ` Jan Kara 2020-07-17 3:49 ` Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 16/22] fsnotify: remove check that source dentry is positive Amir Goldstein 2020-07-16 13:13 ` Jan Kara 2020-07-16 13:29 ` Jan Kara 2020-07-16 13:54 ` Amir Goldstein 2020-07-16 14:06 ` Jan Kara 2020-07-16 8:42 ` [PATCH v5 17/22] fsnotify: send MOVE_SELF event with parent/name info Amir Goldstein 2020-07-16 13:45 ` Jan Kara [this message] 2020-07-16 13:59 ` Amir Goldstein 2020-07-16 14:10 ` Amir Goldstein 2020-07-16 15:57 ` Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 18/22] fanotify: add basic support for FAN_REPORT_DIR_FID Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 19/22] fanotify: report events with parent dir fid to sb/mount/non-dir marks Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 20/22] fanotify: add support for FAN_REPORT_NAME Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 21/22] fanotify: report parent fid + name + child fid Amir Goldstein 2020-07-16 15:59 ` Jan Kara 2020-07-16 16:08 ` Amir Goldstein 2020-07-16 8:42 ` [PATCH v5 22/22] fanotify: report parent fid " Amir Goldstein 2020-07-16 17:13 ` [PATCH v5 00/22] fanotify events with name info Jan Kara
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=20200716134556.GE5022@quack2.suse.cz \ --to=jack@suse.cz \ --cc=amir73il@gmail.com \ --cc=linux-fsdevel@vger.kernel.org \ --subject='Re: [PATCH v5 17/22] fsnotify: send MOVE_SELF event with parent/name info' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).