From: Horst Birthelmer <horst@birthelmer.de>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Bernd Schubert <bernd@bsbernd.com>,
Jim Harris <jim.harris@nvidia.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mgurtovoy@nvidia.com, ksztyber@nvidia.com,
Luis Henriques <luis@igalia.com>
Subject: Re: Re: [PATCH] fuse: skip lookup during atomic_open() when O_CREAT is set
Date: Mon, 23 Feb 2026 19:55:47 +0100 [thread overview]
Message-ID: <aZyhkJSO7Ae7y1Pv@fedora.fritz.box> (raw)
In-Reply-To: <CAJfpeguoQ4qnvYvv2_-e7POXiPeBR2go_J68S2E6c-YW-1tYbA@mail.gmail.com>
On Mon, Feb 23, 2026 at 04:53:33PM +0100, Miklos Szeredi wrote:
> On Mon, 23 Feb 2026 at 16:37, Bernd Schubert <bernd@bsbernd.com> wrote:
>
> > After the discussion about LOOKUO_HANDLE my impression was actually that
> > we want to use compounds for the atomic open.
>
> I think we want to introduce an atomic operation that does a lookup +
> an optional mknod, lets call this LOOKUP_CREATE_FH, this would return
> a flag indicating whether the file was created or if it existed prior
> to the operation.
>
> Then, instead of the current CREATE operation there would be a
> compound with LOOKUP_CREATE_FH + OPEN.
>
> Does that make sense?
What is wrong with a compound doing LOOKUP + MKNOD + OPEN?
If the fuse server knows how to process that 'group' atomically
in one big step it will do the right thing,
if not, we will call those in series and sort out the data
in kernel afterwards.
If we preserve all flags and the real results we can do pretty
much exactly the same thing that is done at the moment with just
one call to user space.
That was actually what I was experimenting with.
The MKNOD in the middle is optional depending on the O_CREAT flag.
>
> Thanks,
> Miklos
Cheers,
Horst
next prev parent reply other threads:[~2026-02-23 18:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 20:41 [PATCH] fuse: skip lookup during atomic_open() when O_CREAT is set Jim Harris
2026-02-21 15:19 ` Horst Birthelmer
2026-02-23 15:09 ` Miklos Szeredi
2026-02-23 15:36 ` Bernd Schubert
2026-02-23 15:53 ` Miklos Szeredi
2026-02-23 16:43 ` Luis Henriques
2026-02-23 16:48 ` Bernd Schubert
2026-02-23 18:55 ` Horst Birthelmer [this message]
2026-02-24 15:33 ` Miklos Szeredi
2026-02-26 23:11 ` Jim Harris
2026-02-27 7:59 ` Horst Birthelmer
2026-02-23 14:57 ` Miklos Szeredi
2026-02-23 16:41 ` Bernd Schubert
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=aZyhkJSO7Ae7y1Pv@fedora.fritz.box \
--to=horst@birthelmer.de \
--cc=bernd@bsbernd.com \
--cc=jim.harris@nvidia.com \
--cc=ksztyber@nvidia.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luis@igalia.com \
--cc=mgurtovoy@nvidia.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