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 6.12-rc1
Date: Mon, 23 Sep 2024 13:03:48 +0200 [thread overview]
Message-ID: <20240923110348.tbwihs42dxxltabc@quack3> (raw)
Hello Linus,
could you please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git fsnotify_for_v6.12-rc1
to get:
* The implementation of the pre-content fanotify events. These events are
sent before read / write / page fault and the execution is paused until
event listener replies similarly to current fanotify permission events.
Facebook and some other vendors already started to use these events for
implementing hierarchical storage management in their infrastructure.
* Fix of a data race noticed by syzbot
There are some conflicts of this pull with other work in linux-next, mostly
with multigrain timestamp series which I think Christian decided to
postpone in the end so this may be a non-issue in the end. The conflicts
were easy to resolve - two commits both adding a feature flag to .fs_flags
in struct filesystem_type. Anyway currently, the merge with your tree as
of today has only one trivial conflict in mm/filemap.c due to added
includes.
Top of the tree is 6165bfb427a6. The full shortlog is:
Amir Goldstein (8):
fsnotify: introduce pre-content permission event
fsnotify: generate pre-content permission event on open
fanotify: introduce FAN_PRE_ACCESS permission event
fanotify: introduce FAN_PRE_MODIFY permission event
fanotify: pass optional file access range in pre-content event
fanotify: rename a misnamed constant
fanotify: report file range info with pre-content events
fanotify: allow to set errno in FAN_DENY permission response
Jan Kara (1):
fsnotify: Avoid data race between fsnotify_recalc_mask() and fsnotify_object_watched()
Josef Bacik (10):
fanotify: don't skip extra event info if no info_mode is set
fs: add a flag to indicate the fs supports pre-content events
fanotify: add a helper to check for pre content events
fanotify: disable readahead if we have pre-content watches
mm: don't allow huge faults for files with pre content watches
fsnotify: generate pre-content permission event on page fault
bcachefs: add pre-content fsnotify hook to fault
xfs: add pre-content fsnotify hook for write faults
btrfs: disable defrag on pre-content watched files
ext4: enable pre-content events
The diffstat is
fs/bcachefs/fs-io-pagecache.c | 4 ++
fs/bcachefs/fs.c | 2 +-
fs/btrfs/ioctl.c | 9 +++
fs/btrfs/super.c | 3 +-
fs/ext4/super.c | 6 +-
fs/namei.c | 9 +++
fs/notify/fanotify/fanotify.c | 32 ++++++++--
fs/notify/fanotify/fanotify.h | 15 +++++
fs/notify/fanotify/fanotify_user.c | 111 ++++++++++++++++++++++++++------
fs/notify/fsnotify.c | 39 ++++++++---
fs/notify/inotify/inotify_user.c | 2 +-
fs/notify/mark.c | 8 ++-
fs/xfs/xfs_file.c | 4 ++
fs/xfs/xfs_super.c | 2 +-
include/linux/fanotify.h | 20 ++++--
include/linux/fs.h | 1 +
include/linux/fsnotify.h | 58 +++++++++++++++--
include/linux/fsnotify_backend.h | 59 ++++++++++++++++-
include/linux/mm.h | 1 +
include/uapi/linux/fanotify.h | 18 ++++++
mm/filemap.c | 128 +++++++++++++++++++++++++++++++++++--
mm/memory.c | 22 +++++++
mm/nommu.c | 7 ++
mm/readahead.c | 13 ++++
security/selinux/hooks.c | 3 +-
25 files changed, 511 insertions(+), 65 deletions(-)
Thanks
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next reply other threads:[~2024-09-23 11:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 11:03 Jan Kara [this message]
2024-09-23 18:35 ` [GIT PULL] Fsnotify changes for 6.12-rc1 Linus Torvalds
2024-09-23 19:13 ` Jan Kara
2024-09-23 19:36 ` Linus Torvalds
2024-09-24 9:27 ` Jan Kara
2024-09-24 16:33 ` Linus Torvalds
2024-09-25 0:16 ` Gao Xiang
2024-09-25 1:15 ` Linus Torvalds
2024-09-25 11:04 ` Jan Kara
2024-10-16 19:28 ` Josef Bacik
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=20240923110348.tbwihs42dxxltabc@quack3 \
--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