linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Casey Bodley <cbodley@citi.umich.edu>
Cc: bjschuma@netapp.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] NFSD: forget_delegations should use list_for_each_entry_safe
Date: Wed, 14 Dec 2011 17:38:54 -0500	[thread overview]
Message-ID: <20111214223854.GE7623@fieldses.org> (raw)
In-Reply-To: <CAMeBU_0bcXWNBWsJ8Sv2n-53fr8jCSQSs_guOnw8WYHgBFQz4A@mail.gmail.com>

On Wed, Dec 14, 2011 at 03:50:53PM -0500, Casey Bodley wrote:
> On Wed, Dec 14, 2011 at 2:39 PM,  <bjschuma@netapp.com> wrote:
> > From: Bryan Schumaker <bjschuma@netapp.com>
> >
> > Otherwise the for loop could try to use a file recently removed from the
> > file_hashtbl list and oops.
> >
> > Signed-off-by: Bryan Schumaker <bjschuma@netapp.com>
> > ---
> >  fs/nfsd/nfs4state.c |    9 +++++----
> >  1 files changed, 5 insertions(+), 4 deletions(-)
> >
> > diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> > index 19ca9b5..7355fe4 100644
> > --- a/fs/nfsd/nfs4state.c
> > +++ b/fs/nfsd/nfs4state.c
> > @@ -4505,18 +4505,19 @@ void nfsd_forget_openowners(u64 num)
> >  int nfsd_process_n_delegations(u64 num, void (*deleg_func)(struct nfs4_delegation *))
> >  {
> >        int i, count = 0;
> > -       struct nfs4_file *fp;
> > -       struct nfs4_delegation *dp, *next;
> > +       struct nfs4_file *fp, *fnext;
> > +       struct nfs4_delegation *dp, *dnext;
> >
> >        for (i = 0; i < FILE_HASH_SIZE; i++) {
> > -               list_for_each_entry(fp, &file_hashtbl[i], fi_hash) {
> > -                       list_for_each_entry_safe(dp, next, &fp->fi_delegations, dl_perfile) {
> > +               list_for_each_entry_safe(fp, fnext, &file_hashtbl[i], fi_hash) {
> > +                       list_for_each_entry_safe(dp, dnext, &fp->fi_delegations, dl_perfile) {
> >                                deleg_func(dp);
> >                                if (++count == num)
> >                                        return count;
> >                        }
> >                }
> >        }
> > +
> >        return count;
> >  }
> >
> > --
> > 1.7.8
> >
> 
> Confirmed to fix the oops I was getting with fault injection. (tested
> without the previous patch, NFSD: Only reinitilize the recall_lru list
> under the recall lock)

Ah-hah.  Thanks Bryan, and Casey--committed.

--b.

      parent reply	other threads:[~2011-12-14 22:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14 19:39 [PATCH] NFSD: forget_delegations should use list_for_each_entry_safe bjschuma
2011-12-14 20:50 ` Casey Bodley
2011-12-14 21:11   ` Bryan Schumaker
2011-12-14 22:38   ` J. Bruce Fields [this message]

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=20111214223854.GE7623@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=bjschuma@netapp.com \
    --cc=cbodley@citi.umich.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;
as well as URLs for NNTP newsgroup(s).