linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bian Naimeng <biannm@cn.fujitsu.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: linux-nfs@vger.kernel.org, "J. Bruce Fields" <bfields@redhat.com>
Subject: Re: [PATCH 2/2] We should clear NFS_DELEGATED_STATE after return delegation
Date: Wed, 08 Sep 2010 10:37:31 +0800	[thread overview]
Message-ID: <4C86F6EB.5060409@cn.fujitsu.com> (raw)
In-Reply-To: <1283911036.16070.1.camel@heimdal.trondhjem.org>

>>>> diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
>>>> index 36400d3..c0c0320 100644
>>>> --- a/fs/nfs/nfs4proc.c
>>>> +++ b/fs/nfs/nfs4proc.c
>>>> @@ -900,8 +900,18 @@ static int update_open_stateid(struct nfs4_state *state, nfs4_stateid *open_stat
>>>>  
>>>>  	rcu_read_lock();
>>>>  	deleg_cur = rcu_dereference(nfsi->delegation);
>>>> -	if (deleg_cur == NULL)
>>>> +	if (deleg_cur == NULL) {
>>>> +		if (delegation == NULL &&
>>>> +		    test_bit(NFS_DELEGATED_STATE, &state->flags)) {
>>> Any reason why we can't ditch the 'test_bit'?
>>>
>>   Because i am not sure it's ok that we just clear_bit at here.
>>   If you think it's ok, i'd be fine with removing this test_bit.
> 
> How is it different from just clearing the bit?

  Yes, I know there are no difference. 

  I mean maybe we need do more things if state is delegation, not just
  clearing the bit, this the reason why i add the FIXME.

  OK, i will send a new one after remove the test_bit.

> 
>>>> +			/*FIXME: If the state has NFS_DELEGATED_STATE bit, 
>>>> +			 * we catch a race. Maybe should recover its open
>>>> +			 * stateid, here we just clear the NFS_DELEGATED_STATE
>>>> +			 * bit.
>>> Can this ever be called with both deleg_cur==NULL and
>>> open_stateid==NULL? If so, then we still have a bug.
>>>
>>   Yes, i will add a checking. Thanks very much.
>>
>>>> +			 */
>>>> +			clear_bit(NFS_DELEGATED_STATE, &state->flags);
>>>> +		}
>>>>  		goto no_delegation;
>>>> +	}
>>>>  
>>>>  	spin_lock(&deleg_cur->lock);
>>>>  	if (nfsi->delegation != deleg_cur ||
> 
> Cheers
>   Trond
> 
 

-- 
Regards
Bian Naimeng


  reply	other threads:[~2010-09-08  2:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04  9:14 [PATCH 0/2] Fix bug that client use a invaild delegation Bian Naimeng
2010-08-04  9:15 ` [PATCH 1/2] Make lock inode before lock nfs4_state_owner Bian Naimeng
2010-08-04  9:18 ` [PATCH 2/2] We should clear NFS_DELEGATED_STATE after return delegation Bian Naimeng
2010-08-04 12:45   ` Trond Myklebust
2010-08-05  2:26     ` Bian Naimeng
2010-08-05 13:03       ` Trond Myklebust
2010-08-06  4:10         ` Bian Naimeng
2010-08-06 13:30           ` Trond Myklebust
2010-08-16  7:50             ` Bian Naimeng
2010-08-17 23:16               ` Trond Myklebust
2010-08-18  3:17                 ` Bian Naimeng
2010-08-23  7:43                   ` Bian Naimeng
2010-09-01  6:40                 ` Bian Naimeng
2010-09-07 22:04                   ` Trond Myklebust
2010-09-08  1:33                     ` Bian Naimeng
2010-09-08  1:57                       ` Trond Myklebust
2010-09-08  2:37                         ` Bian Naimeng [this message]
2010-09-08  3:11                         ` Bian Naimeng
2010-09-08 20:37                           ` Trond Myklebust
2010-09-09  1:29                             ` Bian Naimeng
2010-11-24  6:27                               ` Bian Naimeng
     [not found]                             ` <1283978245.2905.23.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-12-02  8:32                               ` Li Yewang

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=4C86F6EB.5060409@cn.fujitsu.com \
    --to=biannm@cn.fujitsu.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bfields@redhat.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).