All of lore.kernel.org
 help / color / mirror / Atom feed
From: "bfields@fieldses.org" <bfields@fieldses.org>
To: fanchaoting <fanchaoting@cn.fujitsu.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: PATCH]nfsd: don't run get_file if nfs4_preprocess_stateid_op return error
Date: Wed, 3 Apr 2013 15:20:05 -0400	[thread overview]
Message-ID: <20130403192005.GG6044@fieldses.org> (raw)
In-Reply-To: <5159868A.8080105@cn.fujitsu.com>

Thanks, applying, and adding a cc: for stable.--b.

On Mon, Apr 01, 2013 at 09:07:22PM +0800, fanchaoting wrote:
> we should return error status directly when 
> nfs4_preprocess_stateid_op return error. 
> 
> Signed-off-by: fanchaoting <fanchaoting@cn.fujitsu.com>
> ---
>  fs/nfsd/nfs4proc.c |    8 ++++----
>  1 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/nfsd/nfs4proc.c b/fs/nfsd/nfs4proc.c
> index ae73175..8288b08 100644
> --- a/fs/nfsd/nfs4proc.c
> +++ b/fs/nfsd/nfs4proc.c
> @@ -931,14 +931,14 @@ nfsd4_write(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate,
>  	nfs4_lock_state();
>  	status = nfs4_preprocess_stateid_op(SVC_NET(rqstp),
>  					cstate, stateid, WR_STATE, &filp);
> -	if (filp)
> -		get_file(filp);
> -	nfs4_unlock_state();
> -
>  	if (status) {
> +		nfs4_unlock_state();
>  		dprintk("NFSD: nfsd4_write: couldn't process stateid!\n");
>  		return status;
>  	}
> +	if (filp)
> +		get_file(filp);
> +	nfs4_unlock_state();
>  
>  	cnt = write->wr_buflen;
>  	write->wr_how_written = write->wr_stable_how;
> -- 
> 1.7.1
> 
> 

      reply	other threads:[~2013-04-03 19:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-01 13:07 PATCH]nfsd: don't run get_file if nfs4_preprocess_stateid_op return error fanchaoting
2013-04-03 19:20 ` bfields [this message]

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=20130403192005.GG6044@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=fanchaoting@cn.fujitsu.com \
    --cc=linux-nfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.