mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd@bsbernd.com>
To: Miklos Szeredi <miklos@szeredi.hu>,
	Horst Birthelmer <horst@birthelmer.de>
Cc: 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: [PATCH] fuse: skip lookup during atomic_open() when O_CREAT is set
Date: Mon, 23 Feb 2026 16:36:50 +0100	[thread overview]
Message-ID: <fa1b23a7-1dcb-4141-9334-8f9609bb13f7@bsbernd.com> (raw)
In-Reply-To: <CAJfpegstf_hPN2+jyO_vNfjSqZpUZPJqNg59hGSqTYqyWx1VVg@mail.gmail.com>



On 2/23/26 16:09, Miklos Szeredi wrote:
> On Sat, 21 Feb 2026 at 16:19, Horst Birthelmer <horst@birthelmer.de> wrote:
> 
>> I have been looking at that code lately a lot since I was planning to
>> replace it with a compound.
>> I'm not entirely convinced that your proposal is the right direction.
>> I would involve O_EXCL as well, since that lookup could actually
>> help in that case.
>>
>> Take a look at what Miklos wrote here:
>> https://lore.kernel.org/linux-fsdevel/CAJfpegsDxsMsyfP4a_5H1q91xFtwcEdu9-WBnzWKwjUSrPNdmw@mail.gmail.com/
> 
> Bernd had actual patches, that got sidetracked unfortunately:
> 
> https://lore.kernel.org/all/20231023183035.11035-1-bschubert@ddn.com/


After the discussion about LOOKUO_HANDLE my impression was actually that
we want to use compounds for the atomic open.


Thanks,
Bernd

  reply	other threads:[~2026-02-23 15:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-20 20:41 Jim Harris
2026-02-21 15:19 ` Horst Birthelmer
2026-02-23 15:09   ` Miklos Szeredi
2026-02-23 15:36     ` Bernd Schubert [this message]
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
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=fa1b23a7-1dcb-4141-9334-8f9609bb13f7@bsbernd.com \
    --to=bernd@bsbernd.com \
    --cc=horst@birthelmer.de \
    --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
all inboxes | Powered by JetHome®