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
Subject: Re: [PATCH 2/2] We should clear NFS_DELEGATED_STATE after return delegation
Date: Mon, 16 Aug 2010 15:50:06 +0800	[thread overview]
Message-ID: <4C68EDAE.5000201@cn.fujitsu.com> (raw)
In-Reply-To: <1281101448.3586.11.camel@heimdal.trondhjem.org>

>>>>>> We should clear NFS_DELEGATED_STATE bit for inode->open_states after return delegation.

 ... snip ...

>> +
>> +	list_for_each_entry(state, &nfsi->open_states, inode_states) {
>> +		clear_bit(NFS_DELEGATED_STATE, &state->flags);
>> +	}
>> +
>>  	spin_unlock(&inode->i_lock);
>> -	return 0;
>> +	return err;
>>  }
>>  
> 
> I still don't see why this should be necessary. In the case of a server
> reboot or network partition, the state recovery thread ought to be
> taking care of this for us.
> 

   A open state can be found at nfsi->open_states and owner->so_states always, but
  it not be found at nfsi->open_files until we call nfs4_intent_set_file.

   At _nfs4_do_open, we will invoke nfs4_return_incompatible_delegation to return a 
  delegation,  a open stateid which set NFS_DELEGATED_STATE bit may not be found at
  nfsi->open_files, but it still at nfsi->open_states, so we do not clear 
  NFS_DELEGATED_STATE bit for it.

   Then _nfs4_do_open will find it by nfs4_get_open_state, and we still use it
  as a delegation, some error will occur.

-- 
Regards
Bian Naimeng

> Cheers
>   Trond




  reply	other threads:[~2010-08-16  7:51 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 [this message]
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
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=4C68EDAE.5000201@cn.fujitsu.com \
    --to=biannm@cn.fujitsu.com \
    --cc=Trond.Myklebust@netapp.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).