Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: NeilBrown <neil@brown.name>, Chuck Lever <chuck.lever@oracle.com>
Cc: Olga Kornievskaia <okorniev@redhat.com>,
	Dai Ngo <Dai.Ngo@oracle.com>,  Tom Talpey <tom@talpey.com>,
	linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 10/14] nfsd: open-code nfsd4_vfs_create() into nfsd4_create_file()
Date: Mon, 06 Jul 2026 12:21:38 -0400	[thread overview]
Message-ID: <9316b8ed31910b22bed1856905b26f8c87584afa.camel@kernel.org> (raw)
In-Reply-To: <20260705222032.1240057-11-neilb@ownmail.net>

On Mon, 2026-07-06 at 08:19 +1000, NeilBrown wrote:
> From: NeilBrown <neil@brown.name>
> 
> Having this sub function separate doesn't really add clarity, and merging
> allows for some refactoring and ultimately using a different VFS
> interface.
> 
> Signed-off-by: NeilBrown <neil@brown.name>
> ---
>  fs/nfsd/nfs4proc.c | 76 +++++++++++++++++++++-------------------------
>  1 file changed, 34 insertions(+), 42 deletions(-)
> 
> diff --git a/fs/nfsd/nfs4proc.c b/fs/nfsd/nfs4proc.c
> index 973beda7f161..a34731e1714f 100644
> --- a/fs/nfsd/nfs4proc.c
> +++ b/fs/nfsd/nfs4proc.c
> @@ -201,46 +201,6 @@ static inline bool nfsd4_create_is_exclusive(int createmode)
>  		createmode == NFS4_CREATE_EXCLUSIVE4_1;
>  }
>  
> -static __be32
> -nfsd4_vfs_create(struct svc_fh *fhp, struct dentry **child,
> -		 struct nfsd4_open *open)
> -{
> -	struct file *filp;
> -	struct path path;
> -	int oflags;
> -
> -	oflags = O_CREAT | O_LARGEFILE;
> -	/*
> -	 * For the EXCLUSIVE modes we do our own uniqueness tests
> -	 * so don't want O_EXCL.
> -	 */
> -	if (open->op_createmode == NFS4_CREATE_GUARDED)
> -		oflags |= O_EXCL;
> -
> -	switch (open->op_share_access & NFS4_SHARE_ACCESS_BOTH) {
> -	case NFS4_SHARE_ACCESS_WRITE:
> -		oflags |= O_WRONLY;
> -		break;
> -	case NFS4_SHARE_ACCESS_BOTH:
> -		oflags |= O_RDWR;
> -		break;
> -	default:
> -		oflags |= O_RDONLY;
> -	}
> -
> -	path.mnt = fhp->fh_export->ex_path.mnt;
> -	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));
> -
> -	open->op_filp = filp;
> -	return nfs_ok;
> -}
> -
>  /*
>   * Implement NFSv4's unchecked, guarded, and exclusive create
>   * semantics for regular files. Open state for this new file is
> @@ -363,9 +323,41 @@ nfsd4_create_file(struct svc_rqst *rqstp, struct svc_fh *fhp,
>  	} else if (create_status) {
>  		status = create_status;
>  	} else {
> -		status = nfsd4_vfs_create(fhp, &child, open);
> -		if (status == nfs_ok)
> +		struct file *filp;
> +		struct path path;
> +		int oflags;
> +
> +		oflags = O_CREAT | O_LARGEFILE;
> +		/*
> +		 * For the EXCLUSIVE modes we do our own uniqueness tests
> +		 * so don't want O_EXCL.
> +		 */
> +		if (open->op_createmode == NFS4_CREATE_GUARDED)
> +			oflags |= O_EXCL;
> +
> +		switch (open->op_share_access & NFS4_SHARE_ACCESS_BOTH) {
> +		case NFS4_SHARE_ACCESS_WRITE:
> +			oflags |= O_WRONLY;
> +			break;
> +		case NFS4_SHARE_ACCESS_BOTH:
> +			oflags |= O_RDWR;
> +			break;
> +		default:
> +			oflags |= O_RDONLY;
> +		}
> +
> +		path.mnt = fhp->fh_export->ex_path.mnt;
> +		path.dentry = child;
> +		filp = dentry_create(&path, oflags, open->op_iattr.ia_mode,
> +				     current_cred());
> +		child = path.dentry;
> +
> +		if (IS_ERR(filp)) {
> +			status = nfserrno(PTR_ERR(filp));
> +		} else {
> +			open->op_filp = filp;
>  			open->op_created = open->op_filp->f_mode & FMODE_CREATED;
> +		}
>  	}
>  	end_creating(child);
>  	if (status != nfs_ok)

Reviewed-by: Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2026-07-06 16:21 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-05 22:19 [PATCH v2 00/14] nfsd: refactor nfs4_create_file() NeilBrown
2026-07-05 22:19 ` [PATCH v2 01/14] nfsd: honour client-provided attributes for NFS4_CREATE_EXCLUSIVE4_1 NeilBrown
2026-07-06 16:14   ` Jeff Layton
2026-07-05 22:19 ` [PATCH v2 02/14] nfsd: replace fh_fill_both_attrs() with fh_fill_post_noop() NeilBrown
2026-07-06 16:15   ` Jeff Layton
2026-07-05 22:19 ` [PATCH v2 03/14] nfsd: move fh_want_write() after preamble in nfsd4_create_file() NeilBrown
2026-07-06 16:15   ` Jeff Layton
2026-07-05 22:19 ` [PATCH v2 04/14] nfsd: move more nfs-specific code into preamble of nfsd4_create_file() NeilBrown
2026-07-06 16:16   ` Jeff Layton
2026-07-05 22:19 ` [PATCH v2 05/14] nfsd: remove subtlety from nfsd4_create_file() NeilBrown
2026-07-06 16:16   ` Jeff Layton
2026-07-05 22:19 ` [PATCH v2 06/14] nfsd: in nfsd4_create_file() let VFS report if file was created NeilBrown
2026-07-06 15:52   ` Jeff Layton
2026-07-06 23:28     ` NeilBrown
2026-07-05 22:19 ` [PATCH v2 07/14] nfsd: nfsd4_create_file(): Move NFSD_MAY_CREATE check earlier NeilBrown
2026-07-06 16:19   ` Jeff Layton
2026-07-05 22:19 ` [PATCH v2 08/14] nfsd: always open file in nfsd4_create_file() NeilBrown
2026-07-05 22:19 ` [PATCH v2 09/14] nfsd: reduce range of directory lock " NeilBrown
2026-07-06 16:21   ` Jeff Layton
2026-07-05 22:19 ` [PATCH v2 10/14] nfsd: open-code nfsd4_vfs_create() into nfsd4_create_file() NeilBrown
2026-07-06 16:21   ` Jeff Layton [this message]
2026-07-05 22:19 ` [PATCH v2 11/14] nfsd: move some code out of the d_really_is_negative() branch in nfsd4_create_file() NeilBrown
2026-07-06 16:23   ` Jeff Layton
2026-07-05 22:19 ` [PATCH v2 12/14] nfsd: reduce want-write range " NeilBrown
2026-07-05 22:19 ` [PATCH v2 13/14] nfsd: separate out VFS-specific from from nfsd4_create_file() NeilBrown
2026-07-06 16:00   ` Jeff Layton
2026-07-06 23:29     ` NeilBrown
2026-07-05 22:19 ` [PATCH v2 14/14] nfsd: use do_lookup_open() for non-creating open requests too NeilBrown
2026-07-06 14:36   ` Chuck Lever

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=9316b8ed31910b22bed1856905b26f8c87584afa.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=Dai.Ngo@oracle.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=okorniev@redhat.com \
    --cc=tom@talpey.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