From: Amir Goldstein <amir73il@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: Christian Brauner <brauner@kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>,
linux-unionfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-api@vger.kernel.org
Subject: [RFC][PATCH 0/4] Prepare for supporting more filesystems with fanotify
Date: Tue, 25 Apr 2023 16:01:01 +0300 [thread overview]
Message-ID: <20230425130105.2606684-1-amir73il@gmail.com> (raw)
Jan,
Following up on the FAN_REPORT_ANY_FID proposal [1], here is a shot at an
alternative proposal to seamlessly support more filesystems.
While fanotify relaxes the requirements for filesystems to support
reporting fid to require only the ->encode_fh() operation, there are
currently no new filesystems that meet the relaxed requirements.
I will shortly post patches that allow overlayfs to meet the new
requirements with default overlay configurations.
The overlay and vfs/fanotify patch sets are completely independent.
The are both available on my github branch [2] and there is a simple
LTP test variant that tests reporting fid from overlayfs [3], which
also demonstrates the minor UAPI change of name_to_handle_at(2) for
requesting a non-decodeable file handle by userspace.
Thanks,
Amir.
[1] https://lore.kernel.org/linux-fsdevel/20230417162721.ouzs33oh6mb7vtft@quack3/
[2] https://github.com/amir73il/linux/commits/exportfs_encode_fid
[3] https://github.com/amir73il/ltp/commits/exportfs_encode_fid
Amir Goldstein (4):
exportfs: change connectable argument to bit flags
exportfs: add explicit flag to request non-decodeable file handles
exportfs: allow exporting non-decodeable file handles to userspace
fanotify: support reporting non-decodeable file handles
Documentation/filesystems/nfs/exporting.rst | 4 +--
fs/exportfs/expfs.c | 29 ++++++++++++++++++---
fs/fhandle.c | 20 ++++++++------
fs/nfsd/nfsfh.c | 5 ++--
fs/notify/fanotify/fanotify.c | 4 +--
fs/notify/fanotify/fanotify_user.c | 6 ++---
fs/notify/fdinfo.c | 2 +-
include/linux/exportfs.h | 18 ++++++++++---
include/uapi/linux/fcntl.h | 5 ++++
9 files changed, 67 insertions(+), 26 deletions(-)
--
2.34.1
next reply other threads:[~2023-04-25 13:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 13:01 Amir Goldstein [this message]
2023-04-25 13:01 ` [RFC][PATCH 1/4] exportfs: change connectable argument to bit flags Amir Goldstein
2023-04-26 14:16 ` Chuck Lever
2023-04-25 13:01 ` [RFC][PATCH 2/4] exportfs: add explicit flag to request non-decodeable file handles Amir Goldstein
2023-04-26 14:18 ` Chuck Lever
2023-04-27 15:00 ` Jeff Layton
2023-04-27 15:13 ` Amir Goldstein
2023-04-25 13:01 ` [RFC][PATCH 3/4] exportfs: allow exporting non-decodeable file handles to userspace Amir Goldstein
2023-04-25 13:01 ` [RFC][PATCH 4/4] fanotify: support reporting non-decodeable file handles Amir Goldstein
2023-04-27 11:48 ` Jan Kara
2023-04-27 12:28 ` Amir Goldstein
2023-04-27 14:34 ` Amir Goldstein
2023-04-27 16:34 ` Jan Kara
2023-04-26 13:47 ` [RFC][PATCH 0/4] Prepare for supporting more filesystems with fanotify Chuck Lever
2023-04-27 4:57 ` Amir Goldstein
2023-04-27 15:13 ` Jeff Layton
2023-04-27 15:52 ` Amir Goldstein
2023-04-27 16:36 ` Jeff Layton
2023-04-27 19:11 ` Amir Goldstein
2023-04-27 19:26 ` Jeff Layton
2023-04-28 11:40 ` Jan Kara
2023-04-28 12:15 ` Jeff Layton
2023-04-28 12:31 ` Jan Kara
2023-04-28 12:33 ` Amir Goldstein
2023-04-29 14:45 ` Chuck Lever
2023-04-29 17:26 ` Amir Goldstein
2023-05-01 18:48 ` Amir Goldstein
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=20230425130105.2606684-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).