RFC: Set backing file at lookup
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 2 patches 2 repliesIn review
Patches in v1 No applies recorded yet
None of the 2 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] RFC: Set backing file at lookup
Based on our discussion, I put together two simple patches.
The first adds an optional extra parameter to FUSE_LOOKUP outargs. This allows the daemon to set a backing file at lookup time on a successful lookup.
I then looked at which opcodes do not require a file handle. The simplest seem to be FUSE_MKDIR and FUSE_RMDIR. So I implemented passthrough handling for these opcodes in the second patch.
Both patches sit on top of Amir's tree at:
https://github.com/amir73il/linux/commit/ceaf7f16452f6aaf7993279b1c10e727d6bf6a32
Thoughts?
Paul
Paul Lawrence (2):
fuse: Allow backing file to be set at lookup (WIP)
fuse: Add passthrough for mkdir and rmdir (WIP)
fs/fuse/dir.c | 31 +++++++++++++--- fs/fuse/fuse_i.h | 14 ++++++- fs/fuse/iomode.c | 41 ++++++++++++++++++-- fs/fuse/passthrough.c | 78 ++++++++++++++++++++++++++++++++++----- include/uapi/linux/fuse.h | 6 +++ 5 files changed, 150 insertions(+), 20 deletions(-)
Signature · 1 line
2.50.1.565.gc32cd1483b-goog