public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "bfields@fieldses.org" <bfields@fieldses.org>
To: fanchaoting <tingchaofan@gmail.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 2/2] nfsd: remove some useless code
Date: Thu, 11 Apr 2013 10:42:20 -0400	[thread overview]
Message-ID: <20130411144220.GF7081@fieldses.org> (raw)
In-Reply-To: <5166B97D.60805@gmail.com>

On Thu, Apr 11, 2013 at 09:24:13PM +0800, fanchaoting wrote:
> 
> the "list_empty(&oo->oo_owner.so_stateids)" is aways true ,
> so we remove it.

Thanks!  Applying.--b.

> 
>  Signed-off-by: fanchaoting <fanchaoting@cn.fujitsu.com>
> ---
>  fs/nfsd/nfs4state.c |    3 +--
>  1 files changed, 1 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> index 2e27430..e9f1d37 100644
> --- a/fs/nfsd/nfs4state.c
> +++ b/fs/nfsd/nfs4state.c
> @@ -3830,8 +3830,7 @@ nfsd4_close(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate,
>  			 * In the 4.0 case we need to keep the owners around a
>  			 * little while to handle CLOSE replay.
>  			 */
> -			if (list_empty(&oo->oo_owner.so_stateids))
> -				move_to_close_lru(oo, SVC_NET(rqstp));
> +			move_to_close_lru(oo, SVC_NET(rqstp));
>  		}
>  	}
>  out:
> -- 
> 1.7.1
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 
> 

      reply	other threads:[~2013-04-11 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09  6:06 [PATCH] nfsd: remove some useless code fanchaoting
2013-04-11 13:24 ` [PATCH 2/2] " fanchaoting
2013-04-11 14:42   ` 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=20130411144220.GF7081@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tingchaofan@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