From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] fsnotify changes for v5.3-rc1
Date: Tue, 9 Jul 2019 11:16:43 +0200 [thread overview]
Message-ID: <20190709091643.GA5903@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.3-rc1
The pull contains a cleanups of fsnotify name removal hook and also a patch
to disable fanotify permission events for 'proc' filesystem.
Top of the tree is 7377f5bec133. The full shortlog is:
Amir Goldstein (10):
fsnotify: add empty fsnotify_{unlink,rmdir}() hooks
btrfs: call fsnotify_rmdir() hook
rpc_pipefs: call fsnotify_{unlink,rmdir}() hooks
tracefs: call fsnotify_{unlink,rmdir}() hooks
devpts: call fsnotify_unlink() hook
debugfs: simplify __debugfs_remove_file()
debugfs: call fsnotify_{unlink,rmdir}() hooks
configfs: call fsnotify_rmdir() hook
fsnotify: move fsnotify_nameremove() hook out of d_delete()
fsnotify: get rid of fsnotify_nameremove()
Jan Kara (1):
fanotify: Disallow permission events for proc filesystem
The diffstat is
fs/afs/dir_silly.c | 5 -----
fs/btrfs/ioctl.c | 4 +++-
fs/configfs/dir.c | 3 +++
fs/dcache.c | 2 --
fs/debugfs/inode.c | 21 ++++++++++---------
fs/devpts/inode.c | 1 +
fs/namei.c | 2 ++
fs/nfs/unlink.c | 6 ------
fs/notify/fanotify/fanotify_user.c | 22 ++++++++++++++++++++
fs/notify/fsnotify.c | 41 --------------------------------------
fs/proc/root.c | 2 +-
fs/tracefs/inode.c | 3 +++
include/linux/fs.h | 1 +
include/linux/fsnotify.h | 26 ++++++++++++++++++++++++
include/linux/fsnotify_backend.h | 4 ----
net/sunrpc/rpc_pipe.c | 4 ++++
16 files changed, 76 insertions(+), 71 deletions(-)
Thanks
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next reply other threads:[~2019-07-09 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 9:16 Jan Kara [this message]
2019-07-11 4:40 ` [GIT PULL] fsnotify changes for v5.3-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=20190709091643.GA5903@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 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).