From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Fanotify changes for v5.1-rc1
Date: Fri, 1 Mar 2019 16:13:00 +0100 [thread overview]
Message-ID: <20190301151300.GB15758@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_v5.1-rc1
to get support for fanotify directory events and changes to make waiting
for fanotify permission event response killable.
Top of the tree is b51905798195. The full shortlog is:
Amir Goldstein (17):
fsnotify: annotate directory entry modification events
fsnotify: remove dirent events from FS_EVENTS_POSS_ON_CHILD mask
fsnotify: send all event types to super block marks
fsnotify: move mask out of struct fsnotify_event
fanotify: rename struct fanotify_{,perm_}event_info
fanotify: open code fill_event_metadata()
fanotify: encode file identifier for FAN_REPORT_FID
fanotify: copy event fid info to user
fanotify: enable FAN_REPORT_FID init flag
fanotify: cache fsid in fsnotify_mark_connector
vfs: add vfs_get_fsid() helper
fanotify: use vfs_get_fsid() helper instead of vfs_statfs()
fsnotify: report FS_ISDIR flag with MOVE_SELF and DELETE_SELF events
fanotify: check FS_ISDIR flag instead of d_is_dir()
fanotify: support events with data type FSNOTIFY_EVENT_INODE
fanotify: add support for create/attrib/move/delete events
fanotify: report FAN_ONDIR to listener with FAN_REPORT_FID
Jan Kara (8):
fanotify: Select EXPORTFS
fanotify: Fold dequeue_event() into process_access_response()
fanotify: Move locking inside get_one_event()
fsnotify: Create function to remove event from notification list
fanotify: Simplify cleaning of access_list
fanotify: Track permission event state
fanotify: Use interruptible wait when waiting for permission events
fanotify: Make waits for fanotify events only killable
The diffstat is
fs/notify/fanotify/Kconfig | 1 +
fs/notify/fanotify/fanotify.c | 267 +++++++++++++++++++++----
fs/notify/fanotify/fanotify.h | 116 +++++++++--
fs/notify/fanotify/fanotify_user.c | 373 ++++++++++++++++++++++++-----------
fs/notify/fsnotify.c | 15 +-
fs/notify/inotify/inotify.h | 1 +
fs/notify/inotify/inotify_fsnotify.c | 18 +-
fs/notify/inotify/inotify_user.c | 5 +-
fs/notify/mark.c | 42 +++-
fs/notify/notification.c | 42 ++--
fs/statfs.c | 14 ++
include/linux/fanotify.h | 26 ++-
include/linux/fsnotify.h | 73 +++++--
include/linux/fsnotify_backend.h | 67 ++++---
include/linux/statfs.h | 3 +
include/uapi/linux/fanotify.h | 29 +++
16 files changed, 828 insertions(+), 264 deletions(-)
Thanks
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next reply other threads:[~2019-03-01 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 15:13 Jan Kara [this message]
2019-03-07 17:50 ` [GIT PULL] Fanotify changes for v5.1-rc1 pr-tracker-bot
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=20190301151300.GB15758@quack2.suse.cz \
--to=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 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).