Skip to content

RFC Prepare for supporting more filesystems with fanotify

Amir Goldstein linux-api linux-fsdevel linux-nfs linux-unionfs 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest4 patches 22 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4exportfs: change connectable argument to bit flagsfs/exportfs/expfs.c fs/nfsd/nfsfh.c include/linux/exportfs.h+16 -61 reply
2/4exportfs: add explicit flag to request non-decodeable file handlesDocumentation/filesystems/nfs/exporting.rst fs/exportfs/expfs.c fs/notify/fanotify/fanotify.c +2 more+32 -83 replies
3/4exportfs: allow exporting non-decodeable file handles to userspacefs/fhandle.c include/uapi/linux/fcntl.h+17 -80 replies
4/4fanotify: support reporting non-decodeable file handlesfs/notify/fanotify/fanotify.c fs/notify/fanotify/fanotify_user.c+4 -64 replies

Reviews trailers per patch

None of the 4 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.

PatchChuck Lever
SeriesA-b
1/4
2/4
3/4
4/4

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [RFC][PATCH 0/4] Prepare for supporting more filesystems with fanotify

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(-)
Signature · 1 line
2.34.1