linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@primarydata.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: bfields@redhat.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/2] nfsd: remove_stid can be incorporated into nfs4_put_delegation
Date: Mon, 04 Nov 2013 20:05:08 -0800	[thread overview]
Message-ID: <52786E74.8030505@primarydata.com> (raw)
In-Reply-To: <20131104224758.GB8828@fieldses.org>

On 2013-11-04 14:47, J. Bruce Fields wrote:
> On Tue, Oct 15, 2013 at 09:58:00AM +0300, Benny Halevy wrote:
>> All calls to nfs4_put_delegation are preceded with remove_stid.
> 
> Whoops, no, we missed the nfs4_put_delegation call in
> fs/nfsd/nfs4callback.c.
> 
> Noticed because some pynfs tests triggered idr warnings about freeing
> the same id twice.
> 
> I guess I'll revert.

OK.

Benny

> 
> --b.
> 
>>
>> Signed-off-by: Benny Halevy <bhalevy@primarydata.com>
>> ---
>>  fs/nfsd/nfs4state.c | 4 +---
>>  1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
>> index b8f3c7e..93160b6 100644
>> --- a/fs/nfsd/nfs4state.c
>> +++ b/fs/nfsd/nfs4state.c
>> @@ -410,6 +410,7 @@ static void nfs4_free_stid(struct kmem_cache *slab, struct nfs4_stid *s)
>>  void
>>  nfs4_put_delegation(struct nfs4_delegation *dp)
>>  {
>> +	remove_stid(&dp->dl_stid);
>>  	if (atomic_dec_and_test(&dp->dl_count)) {
>>  		nfs4_free_stid(deleg_slab, &dp->dl_stid);
>>  		num_delegations--;
>> @@ -450,14 +451,12 @@ static void unhash_stid(struct nfs4_stid *s)
>>  static void destroy_revoked_delegation(struct nfs4_delegation *dp)
>>  {
>>  	list_del_init(&dp->dl_recall_lru);
>> -	remove_stid(&dp->dl_stid);
>>  	nfs4_put_delegation(dp);
>>  }
>>  
>>  static void destroy_delegation(struct nfs4_delegation *dp)
>>  {
>>  	unhash_delegation(dp);
>> -	remove_stid(&dp->dl_stid);
>>  	nfs4_put_delegation(dp);
>>  }
>>  
>> @@ -3157,7 +3156,6 @@ static void nfsd4_open_deleg_none_ext(struct nfsd4_open *open, int status)
>>  	open->op_delegate_type = NFS4_OPEN_DELEGATE_READ;
>>  	return;
>>  out_free:
>> -	remove_stid(&dp->dl_stid);
>>  	nfs4_put_delegation(dp);
>>  out_no_deleg:
>>  	open->op_delegate_type = NFS4_OPEN_DELEGATE_NONE;
>> -- 
>> 1.8.3.1
>>

  reply	other threads:[~2013-11-05  4:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <525CE652.3070704@primarydata.com>
2013-10-15  6:56 ` [PATCH 0/2] nfsd: cleanup nfs4_put_delegation Benny Halevy
2013-10-15  6:57   ` [PATCH 1/2] nfsd: nfs4_open_delegation needs to remove_stid rather than unhash_stid Benny Halevy
2013-10-28 19:56     ` J. Bruce Fields
2013-10-15  6:58   ` [PATCH 2/2] nfsd: remove_stid can be incorporated into nfs4_put_delegation Benny Halevy
2013-10-28 20:03     ` J. Bruce Fields
2013-11-04 22:47     ` J. Bruce Fields
2013-11-05  4:05       ` Benny Halevy [this message]
2013-11-07 17:02         ` Christoph Hellwig
2013-11-07 17:05           ` J. Bruce Fields
2013-11-07 17:19             ` Christoph Hellwig
2013-11-07 17:47               ` Christoph Hellwig
2013-11-07 20:01           ` Benny Halevy
2013-11-07 21:36             ` Christoph Hellwig

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=52786E74.8030505@primarydata.com \
    --to=bhalevy@primarydata.com \
    --cc=bfields@fieldses.org \
    --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).