From: Jimmy Zuber <jamz@amazon.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: <fuse-devel@lists.linux.dev>, <linux-kselftest@vger.kernel.org>,
"Shuah Khan" <shuah@kernel.org>,
Bernd Schubert <bernd@bsbernd.com>,
Jim Harris <jiharris@nvidia.com>,
Horst Birthelmer <horst@birthelmer.de>,
Luis Henriques <luis@igalia.com>
Subject: [PATCH 0/2] fuse: skip LOOKUP before exclusive create
Date: Tue, 20 Oct 2026 15:34:30 +0000 [thread overview]
Message-ID: <20261020153432.3812719-1-jamz@amazon.com> (raw)
mkdir(), mknod(), symlink(), link() and renameat2() with RENAME_NOREPLACE
look the new name up with FUSE_LOOKUP before sending the request. This
series adds an INIT flag, FUSE_EXCL_CREATE, with which the server fails
these requests with -EEXIST for an existing name, so the kernel can skip
the LOOKUP.
Tested with the new selftest under UML and KVM.
Jimmy Zuber (2):
fuse: skip LOOKUP before exclusive create
selftests/fuse: test FUSE_EXCL_CREATE
fs/fuse/dir.c | 10 +
fs/fuse/fuse_i.h | 3 +
fs/fuse/inode.c | 4 +-
include/uapi/linux/fuse.h | 10 +-
.../selftests/filesystems/fuse/.gitignore | 1 +
.../selftests/filesystems/fuse/Makefile | 3 +-
.../filesystems/fuse/excl_create_test.c | 339 ++++++++++++++++++
7 files changed, 367 insertions(+), 3 deletions(-)
create mode 100644 tools/testing/selftests/filesystems/fuse/excl_create_test.c
base-commit: b776cbe24cc1b79c7f5101762b0069b3f48b6a4b
--
2.50.1
next reply other threads:[~2026-10-20 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 15:34 Jimmy Zuber [this message]
2026-10-20 15:34 ` [PATCH 1/2] fuse: skip LOOKUP before exclusive create Jimmy Zuber
2026-10-20 15:34 ` [PATCH 2/2] selftests/fuse: test FUSE_EXCL_CREATE Jimmy Zuber
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=20261020153432.3812719-1-jamz@amazon.com \
--to=jamz@amazon.com \
--cc=bernd@bsbernd.com \
--cc=fuse-devel@lists.linux.dev \
--cc=horst@birthelmer.de \
--cc=jiharris@nvidia.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=luis@igalia.com \
--cc=miklos@szeredi.hu \
--cc=shuah@kernel.org \
/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