From: Paul Lawrence <paullawrence@google.com>
To: amir73il@gmail.com
Cc: bernd.schubert@fastmail.fm, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, miklos@szeredi.hu,
paullawrence@google.com
Subject: [PATCH 0/2] RFC: Set backing file at lookup
Date: Mon, 4 Aug 2025 10:32:26 -0700 [thread overview]
Message-ID: <20250804173228.1990317-1-paullawrence@google.com> (raw)
In-Reply-To: <CAOQ4uxhmA862ZPAXd=g3vKJAvwAdobAnB--7MqHV87Vmh0USFw@mail.gmail.com>
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(-)
--
2.50.1.565.gc32cd1483b-goog
next prev parent reply other threads:[~2025-08-04 17:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 22:14 [PATCH v1 0/2] RFC: Extend fuse-passthrough to directories Paul Lawrence
2025-06-17 22:14 ` [PATCH v1 1/2] fuse: Add backing file option to lookup Paul Lawrence
2025-06-18 13:46 ` kernel test robot
2025-06-17 22:14 ` [PATCH v1 2/2] fuse: open/close backing file Paul Lawrence
2025-06-18 11:01 ` [PATCH v1 0/2] RFC: Extend fuse-passthrough to directories Amir Goldstein
2025-06-19 19:50 ` Paul Lawrence
2025-06-19 20:29 ` Amir Goldstein
2025-07-14 15:20 ` Amir Goldstein
2025-07-22 21:13 ` Paul Lawrence
2025-07-23 16:53 ` Amir Goldstein
2025-07-23 18:30 ` Paul Lawrence
2025-07-24 19:51 ` Amir Goldstein
2025-08-04 17:32 ` Paul Lawrence [this message]
2025-08-04 17:32 ` [PATCH 1/2] fuse: Allow backing file to be set at lookup (WIP) Paul Lawrence
2025-08-10 14:21 ` Amir Goldstein
2025-08-04 17:32 ` [PATCH 2/2] fuse: Add passthrough for mkdir and rmdir (WIP) Paul Lawrence
2025-08-10 15:40 ` Amir Goldstein
2025-08-10 13:25 ` [PATCH 0/2] RFC: Set backing file at lookup Amir Goldstein
2025-08-10 14:32 ` Amir Goldstein
2026-03-18 18:12 ` [PATCH v1 0/2] RFC: Extend fuse-passthrough to directories Joanne Koong
2026-03-23 17:08 ` Paul Lawrence
2026-03-23 22:24 ` Joanne Koong
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=20250804173228.1990317-1-paullawrence@google.com \
--to=paullawrence@google.com \
--cc=amir73il@gmail.com \
--cc=bernd.schubert@fastmail.fm \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®