linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mi Jinlong <mijinlong@cn.fujitsu.com>
To: Benny Halevy <bhalevy@panasas.com>,
	"J. Bruce Fields" <bfields@redhat.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	NFS <linux-nfs@vger.kernel.org>,
	andros@netapp.com
Subject: Re: [PATCH] nfsd41: modify the members value of nfsd4_op_flags
Date: Fri, 18 Feb 2011 09:09:54 +0800	[thread overview]
Message-ID: <4D5DC6E2.5070307@cn.fujitsu.com> (raw)
In-Reply-To: <4D5D259B.9040605@panasas.com>



Benny Halevy 写道:
> BTW, any particular reason you sent this to Chuck and not Bruce <bfields@redhat.com>
> who's the nfs server maintainer?

  Sorry for my mistake. 

> 
> On 2011-02-17 04:02, Mi Jinlong wrote:
>> The members of nfsd4_op_flags, (ALLOWED_WITHOUT_FH | ALLOWED_ON_ABSENT_FS)
>> equals to  ALLOWED_AS_FIRST_OP, maybe that's not what we want.
>>
>> OP_PUTROOTFH with op_flags = ALLOWED_WITHOUT_FH | ALLOWED_ON_ABSENT_FS,
>> can't appears as the first operation with out SEQUENCE ops.
>>
>> This patch modify the wrong value of ALLOWED_WITHOUT_FH etc which 
>> was introduced by f9bb94c4.
>>
>> Signed-off-by: Mi Jinlong <mijinlong@cn.fujitsu.com>
>> ---
>>  fs/nfsd/nfs4proc.c |    6 +++---
>>  1 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/nfsd/nfs4proc.c b/fs/nfsd/nfs4proc.c
>> index db52546..8605d38 100644
>> --- a/fs/nfsd/nfs4proc.c
>> +++ b/fs/nfsd/nfs4proc.c
>> @@ -983,9 +983,9 @@ static inline void nfsd4_increment_op_stats(u32 opnum)
>>  typedef __be32(*nfsd4op_func)(struct svc_rqst *, struct nfsd4_compound_state *,
>>  			      void *);
>>  enum nfsd4_op_flags {
>> -	ALLOWED_WITHOUT_FH = 1 << 0,	/* No current filehandle required */
>> -	ALLOWED_ON_ABSENT_FS = 2 << 0,	/* ops processed on absent fs */
>> -	ALLOWED_AS_FIRST_OP = 3 << 0,	/* ops reqired first in compound */
>> +	ALLOWED_WITHOUT_FH = 1 << 1,	/* No current filehandle required */
>> +	ALLOWED_ON_ABSENT_FS = 1 << 2,	/* ops processed on absent fs */
>> +	ALLOWED_AS_FIRST_OP = 1 << 3,	/* ops reqired first in compound */
> 
> Right, just 1 << {0,1,2} would make more sense :)

  Thanks for your advice.

--------------------------------------------

  reply	other threads:[~2011-02-18  1:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17  9:02 [PATCH] nfsd41: modify the members value of nfsd4_op_flags Mi Jinlong
2011-02-17 13:41 ` Benny Halevy
2011-02-18  1:09   ` Mi Jinlong [this message]
2011-03-07 17:11     ` J. Bruce Fields

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=4D5DC6E2.5070307@cn.fujitsu.com \
    --to=mijinlong@cn.fujitsu.com \
    --cc=andros@netapp.com \
    --cc=bfields@redhat.com \
    --cc=bhalevy@panasas.com \
    --cc=chuck.lever@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).