linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] Two fixes for NFS RCU-walk support
Date: Mon, 04 Aug 2014 16:24:00 +1000	[thread overview]
Message-ID: <20140804062225.7621.70050.stgit@notabene.brown> (raw)

Thanks to the Feng Wu and the kbuild test robot I see
that some uses for rcu_dereference are wrong.
This two patches resolve the issue and also fix an
embarrassing but harmless bug.

---

NeilBrown (2):
      NFS: fix two problems in lookup_revalidate in RCU-walk
      SUNRPC: remove all refcounting of groupinfo from rpcauth_lookupcred


 fs/nfs/dir.c      |    8 ++++----
 net/sunrpc/auth.c |    8 +-------
 2 files changed, 5 insertions(+), 11 deletions(-)

-- 
Signature


             reply	other threads:[~2014-08-04  6:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04  6:24 NeilBrown [this message]
2014-08-04  6:24 ` [PATCH 2/2] SUNRPC: remove all refcounting of groupinfo from rpcauth_lookupcred NeilBrown
2014-08-04  6:24 ` [PATCH 1/2] NFS: fix two problems in lookup_revalidate in RCU-walk NeilBrown

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=20140804062225.7621.70050.stgit@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.com \
    /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).