Linux NFS development
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Andrew Elble <aweits@rit.edu>
Cc: linux-nfs@vger.kernel.org, Eric Meddaugh <etmsys@rit.edu>
Subject: Re: [PATCH] NFS: fix clp->cl_revoked list deletion causing softlock in nfsd
Date: Wed, 25 Feb 2015 17:53:02 -0500	[thread overview]
Message-ID: <20150225225302.GA20495@fieldses.org> (raw)

Thanks, applying for 3.20.

--b.

> commit 2d4a532d385f ("nfsd: ensure that clp->cl_revoked list is
> protected by clp->cl_lock") removed the use of the reaplist to
> clean out clp->cl_revoked. It failed to change list_entry() to
> walk clp->cl_revoked.next instead of reaplist.next
> 
> Fixes: 2d4a532d385f ("nfsd: ensure that clp->cl_revoked list is protected by clp->cl_lock")
> Cc: stable@vger.kernel.org
> Reported-by: Eric Meddaugh <etmsys@rit.edu>
> Tested-by: Eric Meddaugh <etmsys@rit.edu>
> Signed-off-by: Andrew Elble <aweits@rit.edu>
> ---
>  fs/nfsd/nfs4state.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> index f6b2a09f793f..d2f2c37dc2db 100644
> --- a/fs/nfsd/nfs4state.c
> +++ b/fs/nfsd/nfs4state.c
> @@ -1638,7 +1638,7 @@ __destroy_client(struct nfs4_client *clp)
>  		nfs4_put_stid(&dp->dl_stid);
>  	}
>  	while (!list_empty(&clp->cl_revoked)) {
> -		dp = list_entry(reaplist.next, struct nfs4_delegation, dl_recall_lru);
> +		dp = list_entry(clp->cl_revoked.next, struct nfs4_delegation, dl_recall_lru);
>  		list_del_init(&dp->dl_recall_lru);
>  		nfs4_put_stid(&dp->dl_stid);
>  	}
> -- 
> 2.2.1

             reply	other threads:[~2015-02-25 22:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25 22:53 J. Bruce Fields [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-02-25 13:42 [PATCH] NFS: fix clp->cl_revoked list deletion causing softlock in nfsd Andrew Elble
2015-02-26  0:30 ` Jeff Layton
2015-02-26 14:28 ` Jeff Layton

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=20150225225302.GA20495@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=1424871775-98137-1-git-send-email-aweits@rit.edu \
    --cc=aweits@rit.edu \
    --cc=etmsys@rit.edu \
    --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