mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@hammerspace.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Please pull NFS client bugfixes for 5.13
Date: Sun, 13 Jun 2021 15:36:38 +0000	[thread overview]
Message-ID: <a163fa3530e0c39ae83bdbee68dd189b1d15fe27.camel@hammerspace.com> (raw)

Hi Linus,

The following changes since commit 8124c8a6b35386f73523d27eacb71b5364a68c4c:

  Linux 5.13-rc4 (2021-05-30 11:58:25 -1000)

are available in the Git repository at:

  git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-5.13-3

for you to fetch changes up to c3aba897c6e67fa464ec02b1f17911577d619713:

  NFSv4: Fix second deadlock in nfs4_evict_inode() (2021-06-03 10:14:42 -0400)

Cheers
  Trond

----------------------------------------------------------------
NFS client bugfixes for Linux 5.13

Highlights include

Stable fixes:
- Fix use-after-free in nfs4_init_client()

Bugfixes:
- Fix deadlock between nfs4_evict_inode() and nfs4_opendata_get_inode()
- Fix second deadlock in nfs4_evict_inode()
- nfs4_proc_set_acl should not change the value of NFS_CAP_UIDGID_NOMAP
- Fix setting of the NFS_CAP_SECURITY_LABEL capability

----------------------------------------------------------------
Anna Schumaker (1):
      NFS: Fix use-after-free in nfs4_init_client()

Chuck Lever (1):
      NFS: FMODE_READ and friends are C macros, not enum types

Dai Ngo (1):
      NFSv4: nfs4_proc_set_acl needs to restore NFS_CAP_UIDGID_NOMAP on error.

Dan Carpenter (1):
      NFS: Fix a potential NULL dereference in nfs_get_client()

Scott Mayhew (1):
      NFS: Ensure the NFS_CAP_SECURITY_LABEL capability is set when appropriate

Trond Myklebust (2):
      NFSv4: Fix deadlock between nfs4_evict_inode() and nfs4_opendata_get_inode()
      NFSv4: Fix second deadlock in nfs4_evict_inode()

 fs/nfs/client.c     |  2 +-
 fs/nfs/nfs4_fs.h    |  1 +
 fs/nfs/nfs4client.c |  2 +-
 fs/nfs/nfs4proc.c   | 37 ++++++++++++++++++++++++++++++-------
 fs/nfs/nfstrace.h   |  4 ----
 5 files changed, 33 insertions(+), 13 deletions(-)


-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com



             reply	other threads:[~2021-06-13 15:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-13 15:36 Trond Myklebust [this message]
2021-06-13 20:17 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2021-05-28 14:15 Trond Myklebust
2021-05-28 19:00 ` 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=a163fa3530e0c39ae83bdbee68dd189b1d15fe27.camel@hammerspace.com \
    --to=trondmy@hammerspace.com \
    --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

all inboxes | Powered by JetHome®