public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Paulo Alcantara <pc@manguebit.org>
Cc: NeilBrown <neil@brown.name>,
	smfrench@gmail.com, David Howells <dhowells@redhat.com>,
	linux-fsdevel@vger.kernel.org, linux-cifs@vger.kernel.org
Subject: Re: [PATCH 2/2] smb: client: add support for O_TMPFILE
Date: Wed, 8 Apr 2026 07:57:19 +0100	[thread overview]
Message-ID: <20260408065719.GF3836593@ZenIV> (raw)
In-Reply-To: <98c9845554e2e6a79965d68ba8ae722b@manguebit.org>

On Mon, Apr 06, 2026 at 10:28:51PM -0300, Paulo Alcantara wrote:

> IIUC, this is what we currently have
> 
> * cifs_atomic_open()
> 
>   init state: in-lookup or hashed-negative
>   [d_drop() + d_add()]
>   end state: hashed-positive
> 
> * cifs_tmpfile()
> 
>   init state: unhashed-negative
>   [d_drop() + d_instantiate()]
>   end state: unhashed-positive
> 
> * cifs_create()
> 
>   init state: hashed-negative
>   [d_drop() + d_add()]
>   end state: hashed-positive

IDGI.  Why shouldn't cifs_create() simply do d_instantiate() instead
of that dance, ditto for cifs_tmpfile()?

The only case where you want to change the hashed status is in-lookup
O_CREAT ->atomic_open().  And there it's not d_drop()+d_add() - it's
d_splice_alias().

I'd lift that d_drop() out of cifs_do_create() into the callers and
get rid of it, along with d_add()...

  reply	other threads:[~2026-04-08  6:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-05 21:18 [PATCH 1/2] vfs: introduce d_mark_tmpfile_name() Paulo Alcantara
2026-04-05 21:18 ` [PATCH 2/2] smb: client: add support for O_TMPFILE Paulo Alcantara
2026-04-05 23:32   ` Al Viro
2026-04-05 23:53     ` NeilBrown
2026-04-07  1:28       ` Paulo Alcantara
2026-04-08  6:57         ` Al Viro [this message]
2026-04-08 13:48           ` Paulo Alcantara
2026-04-06  3:23 ` [PATCH 1/2] vfs: introduce d_mark_tmpfile_name() Matthew Wilcox
2026-04-07  1:29   ` Paulo Alcantara

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=20260408065719.GF3836593@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=dhowells@redhat.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=pc@manguebit.org \
    --cc=smfrench@gmail.com \
    /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