From: Luis Henriques <luis@igalia.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Matt Harvey <mharvey@jumptrading.com>,
kernel-dev@igalia.com, Luis Henriques <luis@igalia.com>
Subject: [RFC PATCH 0/1] fuse: restructure requests extensions handling
Date: Mon, 9 Mar 2026 14:59:43 +0000 [thread overview]
Message-ID: <20260309145944.40000-1-luis@igalia.com> (raw)
Hi!
This patch was going to be included in the lookup_handle patchset. But
since it is self-contained and it can eventually be picked independently,
I've decided to send it as a separate RFC.
It basically re-implements the idea of extensions, making it easier to add
new ones: a extension can be simply added to the 'ext_args' array in
fuse_args.
Luis Henriques (1):
fuse: restructure requests extensions handling
fs/fuse/dev.c | 35 +++++++++++++++-
fs/fuse/dir.c | 104 +++++++++++++++++++++--------------------------
fs/fuse/fuse_i.h | 11 ++++-
3 files changed, 89 insertions(+), 61 deletions(-)
next reply other threads:[~2026-03-09 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 14:59 Luis Henriques [this message]
2026-03-09 14:59 ` [RFC PATCH 1/1] " Luis Henriques
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=20260309145944.40000-1-luis@igalia.com \
--to=luis@igalia.com \
--cc=kernel-dev@igalia.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mharvey@jumptrading.com \
--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®