From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] Fsnotify fixes and improvements for 5.11-rc1
Date: Thu, 17 Dec 2020 12:15:45 +0100 [thread overview]
Message-ID: <20201217111545.GC6989@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.11-rc1
to get a few fsnotify fixes from Amir fixing fallout from big fsnotify
overhaul a few months back and an improvement of defaults limiting maximum
number of inotify watches from Waiman.
Top of the tree is fecc4559780d. The full shortlog is:
Amir Goldstein (3):
fsnotify: generalize handle_inode_event()
inotify: convert to handle_inode_event() interface
fsnotify: fix events reported to watching parent and child
Waiman Long (1):
inotify: Increase default inotify.max_user_watches limit to 1048576
The diffstat is
fs/nfsd/filecache.c | 2 +-
fs/notify/dnotify/dnotify.c | 2 +-
fs/notify/fanotify/fanotify.c | 7 +--
fs/notify/fsnotify.c | 107 +++++++++++++++++++++++------------
fs/notify/inotify/inotify.h | 9 ++-
fs/notify/inotify/inotify_fsnotify.c | 51 +++--------------
fs/notify/inotify/inotify_user.c | 31 +++++++---
include/linux/fsnotify_backend.h | 9 +--
kernel/audit_fsnotify.c | 2 +-
kernel/audit_tree.c | 2 +-
kernel/audit_watch.c | 2 +-
11 files changed, 120 insertions(+), 104 deletions(-)
Thanks
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next reply other threads:[~2020-12-17 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 11:15 Jan Kara [this message]
2020-12-17 20:21 ` [GIT PULL] Fsnotify fixes and improvements for 5.11-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=20201217111545.GC6989@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).