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.8-rc1
Date: Mon, 8 Jan 2024 15:07:46 +0100 [thread overview]
Message-ID: <20240108140746.viajl65blnibbyjf@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.8-rc1
to get fanotify changes allowing use of fanotify directory events even for
filesystems such as FUSE which don't report proper fsid.
Top of the tree is 30ad1938326b. The full shortlog is:
Amir Goldstein (2):
fanotify: store fsid in mark instead of in connector
fanotify: allow "weak" fsid when watching a single filesystem
The diffstat is
fs/notify/fanotify/fanotify.c | 34 +++-------
fs/notify/fanotify/fanotify.h | 16 +++++
fs/notify/fanotify/fanotify_user.c | 124 ++++++++++++++++++++++++++++++-------
fs/notify/mark.c | 52 +++-------------
include/linux/fsnotify_backend.h | 14 ++---
5 files changed, 140 insertions(+), 100 deletions(-)
Thanks
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next reply other threads:[~2024-01-08 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 14:07 Jan Kara [this message]
2024-01-10 17:37 ` [GIT PULL] fsnotify changes for 6.8-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=20240108140746.viajl65blnibbyjf@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;
as well as URLs for NNTP newsgroup(s).