From: Benjamin Coddington <bcodding@hammerspace.com>
To: Mike Snitzer <snitzer@kernel.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>, NeilBrown <neil@brown.name>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nfs@vger.kernel.org, Trond Myklebust <trondmy@kernel.org>
Subject: Re: [PATCH v1 3/3] VFS/knfsd: Teach dentry_create() to use atomic_open()
Date: Tue, 18 Nov 2025 13:39:51 -0500 [thread overview]
Message-ID: <A0B89B6B-A025-47EB-A54B-79384ACABBEB@hammerspace.com> (raw)
In-Reply-To: <aRy0Yp-GvUrD3uJY@kernel.org>
On 18 Nov 2025, at 13:01, Mike Snitzer wrote:
> On Tue, Nov 18, 2025 at 11:33:59AM -0500, Benjamin Coddington wrote:
>
>> path.mnt = fhp->fh_export->ex_path.mnt;
>> - path.dentry = child;
>> + path.dentry = *child;
>> filp = dentry_create(&path, oflags, open->op_iattr.ia_mode,
>> current_cred());
>> + *child = path.dentry;
>> +
>> if (IS_ERR(filp))
>> return nfserrno(PTR_ERR(filp));
>>
>
> Given the potential for side-effect due to dentry_create() now using
> atomic_open() if available, I think you'd do well to update the
> comment block above dentry_create to make it clear that the caller
> really should pass along the dentry (regardless of whether
> dentry_create returns an ERR_PTR).
I will update the comment block to make it clear that the dentry you sent on
@path may be changed.
Ben
next prev parent reply other threads:[~2025-11-18 18:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 16:33 [PATCH v1 0/3] Allow knfsd to use atomic_open() Benjamin Coddington
2025-11-18 16:33 ` [PATCH v1 1/3] VFS: move dentry_create() from fs/open.c to fs/namei.c Benjamin Coddington
2025-11-18 16:33 ` [PATCH v1 2/3] VFS: Prepare atomic_open() for dentry_create() Benjamin Coddington
2025-11-18 16:33 ` [PATCH v1 3/3] VFS/knfsd: Teach dentry_create() to use atomic_open() Benjamin Coddington
2025-11-18 18:01 ` Mike Snitzer
2025-11-18 18:39 ` Benjamin Coddington [this message]
2025-11-18 16:58 ` [PATCH v1 0/3] Allow knfsd " Chuck Lever
2025-11-18 17:17 ` Benjamin Coddington
2025-11-18 17:45 ` Trond Myklebust
2025-11-18 21:31 ` Jeff Layton
2025-11-19 1:23 ` NeilBrown
2025-11-19 12:46 ` Benjamin Coddington
2025-11-20 22:26 ` NeilBrown
2025-11-21 1:07 ` Benjamin Coddington
2025-11-26 20:59 ` NeilBrown
2025-11-26 22:06 ` Benjamin Coddington
2025-11-27 0:36 ` NeilBrown
2025-11-27 13:18 ` Benjamin Coddington
2025-11-19 1:32 ` [PATCH v1 2/3] VFS: Prepare atomic_open() for dentry_create() NeilBrown
2025-11-19 13:11 ` Benjamin Coddington
2025-11-19 1:41 ` [PATCH v1 3/3] VFS/knfsd: Teach dentry_create() to use atomic_open() NeilBrown
2025-11-19 13:02 ` Benjamin Coddington
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=A0B89B6B-A025-47EB-A54B-79384ACABBEB@hammerspace.com \
--to=bcodding@hammerspace.com \
--cc=Dai.Ngo@oracle.com \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=snitzer@kernel.org \
--cc=tom@talpey.com \
--cc=trondmy@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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