From: Amir Goldstein <amir73il@gmail.com> To: Jan Kara <jack@suse.cz> Cc: linux-fsdevel@vger.kernel.org Subject: [PATCH v3 00/20] Prep work for fanotify events with name info Date: Wed, 8 Jul 2020 14:11:56 +0300 [thread overview] Message-ID: <20200708111156.24659-21-amir73il@gmail.com> (raw) In-Reply-To: <20200708111156.24659-1-amir73il@gmail.com> Hi Jan, Following patches address your review comments on v2 [1]. Branch is avalable at [2] and test branch of complete work of the moment is available at [3]. Thanks, Amir. Changes sinve v2: - Re-parcel variable size buffer using struct fanotify_info - Move space reservation of _inline_fh_buf to struct fanotify_fid_event - Add Acks on kernfs patch [1] https://lore.kernel.org/linux-fsdevel/20200612093343.5669-1-amir73il@gmail.com/ [2] https://github.com/amir73il/linux/commits/fanotify_prep-v3 [3] https://github.com/amir73il/linux/commits/fanotify_name_fid Amir Goldstein (19): fsnotify: fold fsnotify() call into fsnotify_parent() fsnotify: return non const from fsnotify_data_inode() nfsd: use fsnotify_data_inode() to get the unlinked inode kernfs: do not call fsnotify() with name without a parent inotify: do not use objectid when comparing events fanotify: create overflow event type fanotify: break up fanotify_alloc_event() fsnotify: pass dir argument to handle_event() callback fanotify: generalize the handling of extra event flags fanotify: generalize merge logic of events on dir fanotify: distinguish between fid encode error and null fid fanotify: generalize test for FAN_REPORT_FID fanotify: mask out special event flags from ignored mask fanotify: prepare for implicit event flags in mark mask fanotify: use FAN_EVENT_ON_CHILD as implicit flag on sb/mount/non-dir marks fanotify: remove event FAN_DIR_MODIFY fsnotify: add object type "child" to object type iterator fanotify: use struct fanotify_info to parcel the variable size buffer fanotify: no external fh buffer in fanotify_name_event Mel Gorman (1): fsnotify: Rearrange fast path to minimise overhead when there is no watcher fs/kernfs/file.c | 2 +- fs/nfsd/filecache.c | 8 +- fs/notify/dnotify/dnotify.c | 8 +- fs/notify/fanotify/fanotify.c | 354 ++++++++++++++++----------- fs/notify/fanotify/fanotify.h | 110 +++++++-- fs/notify/fanotify/fanotify_user.c | 110 +++++---- fs/notify/fsnotify.c | 82 ++++--- fs/notify/inotify/inotify.h | 6 +- fs/notify/inotify/inotify_fsnotify.c | 11 +- fs/notify/inotify/inotify_user.c | 4 +- include/linux/fanotify.h | 6 +- include/linux/fsnotify.h | 43 ++-- include/linux/fsnotify_backend.h | 34 ++- include/uapi/linux/fanotify.h | 1 - kernel/audit_fsnotify.c | 10 +- kernel/audit_tree.c | 6 +- kernel/audit_watch.c | 6 +- 17 files changed, 500 insertions(+), 301 deletions(-) -- 2.17.1
prev parent reply other threads:[~2020-07-08 11:12 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-08 11:11 [PATCH v3 01/20] fsnotify: Rearrange fast path to minimise overhead when there is no watcher Amir Goldstein 2020-07-08 11:11 ` [PATCH v3 02/20] fsnotify: fold fsnotify() call into fsnotify_parent() Amir Goldstein 2020-07-08 11:11 ` [PATCH v3 03/20] fsnotify: return non const from fsnotify_data_inode() Amir Goldstein 2020-07-08 11:11 ` [PATCH v3 04/20] nfsd: use fsnotify_data_inode() to get the unlinked inode Amir Goldstein 2020-07-08 11:11 ` [PATCH v3 05/20] kernfs: do not call fsnotify() with name without a parent Amir Goldstein 2020-07-08 11:11 ` [PATCH v3 06/20] inotify: do not use objectid when comparing events Amir Goldstein 2020-07-08 11:11 ` [PATCH v3 07/20] fanotify: create overflow event type Amir Goldstein 2020-07-08 11:11 ` [PATCH v3 08/20] fanotify: break up fanotify_alloc_event() Amir Goldstein 2020-07-08 16:40 ` kernel test robot [not found] ` <202007091516.gofG28uU%lkp@intel.com> 2020-07-09 9:03 ` Amir Goldstein 2020-07-08 11:11 ` [PATCH v3 09/20] fsnotify: pass dir argument to handle_event() callback Amir Goldstein 2020-07-08 11:11 ` [PATCH v3 10/20] fanotify: generalize the handling of extra event flags Amir Goldstein 2020-07-08 11:11 ` [PATCH v3 11/20] fanotify: generalize merge logic of events on dir Amir Goldstein 2020-07-08 11:11 ` [PATCH v3 12/20] fanotify: distinguish between fid encode error and null fid Amir Goldstein 2020-07-08 11:11 ` [PATCH v3 13/20] fanotify: generalize test for FAN_REPORT_FID Amir Goldstein 2020-07-08 11:11 ` [PATCH v3 14/20] fanotify: mask out special event flags from ignored mask Amir Goldstein 2020-07-08 11:11 ` [PATCH v3 15/20] fanotify: prepare for implicit event flags in mark mask Amir Goldstein 2020-07-08 11:11 ` [PATCH v3 16/20] fanotify: use FAN_EVENT_ON_CHILD as implicit flag on sb/mount/non-dir marks Amir Goldstein 2020-07-08 11:11 ` [PATCH v3 17/20] fanotify: remove event FAN_DIR_MODIFY Amir Goldstein 2020-07-08 11:11 ` [PATCH v3 18/20] fsnotify: add object type "child" to object type iterator Amir Goldstein 2020-07-08 11:11 ` [PATCH v3 19/20] fanotify: use struct fanotify_info to parcel the variable size buffer Amir Goldstein 2020-07-08 11:11 ` [PATCH v3 20/20] fanotify: no external fh buffer in fanotify_name_event Amir Goldstein 2020-07-15 15:34 ` Jan Kara 2020-07-15 16:05 ` Amir Goldstein 2020-07-15 16:22 ` Amir Goldstein 2020-07-15 16:24 ` Jan Kara 2020-07-15 17:44 ` Amir Goldstein 2020-07-08 11:11 ` Amir Goldstein [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=20200708111156.24659-21-amir73il@gmail.com \ --to=amir73il@gmail.com \ --cc=jack@suse.cz \ --cc=linux-fsdevel@vger.kernel.org \ --subject='Re: [PATCH v3 00/20] Prep work for fanotify events with 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).