Linux NFS development
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] nfsd bugfixes for 5.3
Date: Wed, 21 Aug 2019 11:06:46 -0400	[thread overview]
Message-ID: <20190821150646.GC22104@fieldses.org> (raw)

Please pull nfsd bugfixes for 5.3 from:

  git://linux-nfs.org/~bfields/linux.git tags/nfsd-5.3-1

Fix nfsd bugs, three in the new nfsd/clients/ code, one in the reply
cache containerization.

--b.

He Zhe (1):
      nfsd4: Fix kernel crash when reading proc file reply_cache_stats

J. Bruce Fields (2):
      nfsd: use i_wrlock instead of rcu for nfsdfs i_private
      nfsd: initialize i_private before d_add

Tetsuo Handa (1):
      nfsd: fix dentry leak upon mkdir failure.

 fs/nfsd/nfscache.c |  2 +-
 fs/nfsd/nfsctl.c   | 19 +++++++++----------
 2 files changed, 10 insertions(+), 11 deletions(-)

             reply	other threads:[~2019-08-21 15:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-21 15:06 J. Bruce Fields [this message]
2019-08-21 20:35 ` [GIT PULL] nfsd bugfixes for 5.3 pr-tracker-bot

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=20190821150646.GC22104@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=torvalds@linux-foundation.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