From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] Fsnotify cleanups
Date: Thu, 7 Jun 2018 17:02:17 +0200 [thread overview]
Message-ID: <20180607150217.jq757ncqopuimbkd@quack2.suse.cz> (raw)
Hello Linus,
could you please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git fsnotify_for_v4.18-rc1
to get several fsnotify cleanups unifying handling of different watch
types.
Top of the tree is 3be4aaf4e2d3. The full shortlog is:
Amir Goldstein (12):
fsnotify: use type id to identify connector object type
fsnotify: remove redundant arguments to handle_event()
fsnotify: introduce marks iteration helpers
fsnotify: generalize iteration of marks by object type
fsnotify: generalize send_to_group()
fanotify: generalize fanotify_should_send_event()
fsnotify: add fsnotify_add_inode_mark() wrappers
fsnotify: introduce prototype struct fsnotify_obj
fsnotify: pass fsnotify_obj instead of **connp argument
fsnotify: pass object and object type to fsnotify_add_mark()
fsnotify: let connector point to abstract fsnotify_obj
fanotify: factor out helpers to add/remove mark
The diffstat is
fs/inode.c | 2 +-
fs/mount.h | 11 ++-
fs/notify/dnotify/dnotify.c | 16 ++--
fs/notify/fanotify/fanotify.c | 46 +++++-----
fs/notify/fanotify/fanotify_user.c | 98 ++++++++-------------
fs/notify/fdinfo.c | 12 +--
fs/notify/fsnotify.c | 160 ++++++++++++++++++++---------------
fs/notify/fsnotify.h | 14 +--
fs/notify/group.c | 2 +-
fs/notify/inotify/inotify.h | 2 -
fs/notify/inotify/inotify_fsnotify.c | 6 +-
fs/notify/inotify/inotify_user.c | 16 ++--
fs/notify/mark.c | 140 ++++++++++++++----------------
include/linux/fs.h | 20 +++--
include/linux/fsnotify_backend.h | 109 +++++++++++++++++++-----
include/linux/fsnotify_obj.h | 18 ++++
kernel/audit_fsnotify.c | 5 +-
kernel/audit_tree.c | 22 +++--
kernel/audit_watch.c | 7 +-
kernel/auditsc.c | 4 +-
20 files changed, 396 insertions(+), 314 deletions(-)
create mode 100644 include/linux/fsnotify_obj.h
Thanks
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next reply other threads:[~2018-06-07 15:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 15:02 Jan Kara [this message]
2018-06-07 16:34 ` [GIT PULL] Fsnotify cleanups Linus Torvalds
2018-06-08 13:27 ` Jan Kara
2018-06-08 20:34 ` Linus Torvalds
2018-06-09 6:57 ` Amir Goldstein
2018-06-09 8:00 ` Amir Goldstein
2018-06-11 16:12 ` Jan Kara
2018-06-11 16:31 ` Amir Goldstein
2018-06-09 17:30 ` Linus Torvalds
2018-06-09 18:46 ` Amir Goldstein
2018-06-10 17:49 ` Amir Goldstein
2018-06-11 13:36 ` Jan Kara
2018-06-11 13:58 ` Amir Goldstein
2018-06-11 16:03 ` Jan Kara
2018-06-11 16:38 ` Amir Goldstein
2018-06-11 19:51 ` Amir Goldstein
2018-06-13 13:21 ` Jan Kara
2018-06-13 13:56 ` Amir Goldstein
2018-06-13 22:17 ` Amir Goldstein
2018-06-22 16:44 ` Jan Kara
2018-06-23 7:42 ` Amir Goldstein
2018-06-11 11:08 ` 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=20180607150217.jq757ncqopuimbkd@quack2.suse.cz \
--to=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.