Linux NFS development
 help / color / mirror / Atom feed
From: Anna Schumaker <anna@kernel.org>
To: linux-nfs@vger.kernel.org, torvalds@linux-foundation.org
Cc: anna@kernel.org
Subject: [GIT PULL] Please pull NFS Client bugfixes for 6.4-rc
Date: Mon, 22 May 2023 14:43:29 -0400	[thread overview]
Message-ID: <20230522184329.5173-1-anna@kernel.org> (raw)

Hi Linus,

The following changes since commit f1fcbaa18b28dec10281551dfe6ed3a3ed80e3d6:

  Linux 6.4-rc2 (2023-05-14 12:51:40 -0700)

are available in the Git repository at:

  git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-6.4-2

for you to fetch changes up to 43439d858bbae244a510de47f9a55f667ca4ed52:

  NFSv4.2: Fix a potential double free with READ_PLUS (2023-05-19 17:11:59 -0400)

----------------------------------------------------------------
NFS Client Bugfixes for Linux 6.4-rc

Stable Fix:
  * Don't change task->tk_status after the call to rpc_exit_task

Other Bugfixes:
  * Convert kmap_atomic() to kmap_local_folio()
  * Fix a potential double free with READ_PLUS

Thanks,
Anna

----------------------------------------------------------------
Anna Schumaker (1):
      NFSv4.2: Fix a potential double free with READ_PLUS

Fabio M. De Francesco (1):
      NFS: Convert kmap_atomic() to kmap_local_folio()

Trond Myklebust (1):
      SUNRPC: Don't change task->tk_status after the call to rpc_exit_task

 fs/nfs/dir.c       |  4 ++--
 fs/nfs/nfs4proc.c  | 12 ++++++++++--
 net/sunrpc/sched.c |  5 ++---
 3 files changed, 14 insertions(+), 7 deletions(-)

             reply	other threads:[~2023-05-22 18:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 18:43 Anna Schumaker [this message]
2023-05-22 19:14 ` [GIT PULL] Please pull NFS Client bugfixes for 6.4-rc 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=20230522184329.5173-1-anna@kernel.org \
    --to=anna@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