All of
 help / color / mirror / Atom feed
From: Christoph Hellwig <>
To: Jens Axboe <>
Cc: Keith Busch <>,, Sagi Grimberg <>,
Subject: [GIT PULL] nvme fixes for Linux 6.0
Date: Thu, 8 Sep 2022 17:35:13 +0200	[thread overview]
Message-ID: <> (raw)

The following changes since commit 748008e1da926a814cc0a054c81ca614408b1b0c:

  block: don't add partitions if GD_SUPPRESS_PART_SCAN is set (2022-09-03 11:29:03 -0600)

are available in the Git repository at:

  git:// tags/nvme-6.0-2022-09-08

for you to fetch changes up to 371a982cd2b01487295cd87abec82357e268457b:

  nvme: requeue aen after firmware activation (2022-09-07 08:38:25 +0200)

nvme fixes for Linux 6.1

 - fix a use after free in nvmet (Bart Van Assche)
 - fix a use after free when detecting digest errors (Sagi Grimberg)
 - fix regression that causes sporadic TCP requests to time out
   (Sagi Grimberg)
 - fix two off by ones errors in the nvmet ZNS support
   (Dennis Maisenbacher)
 - requeue aen after firmware activation (Keith Busch)

Bart Van Assche (1):
      nvmet: fix a use-after-free

Dennis Maisenbacher (1):
      nvmet: fix mar and mor off-by-one errors

Keith Busch (1):
      nvme: requeue aen after firmware activation

Sagi Grimberg (2):
      nvme-tcp: fix UAF when detecting digest errors
      nvme-tcp: fix regression that causes sporadic requests to time out

 drivers/nvme/host/core.c   | 14 +++++++++++---
 drivers/nvme/host/tcp.c    |  7 ++-----
 drivers/nvme/target/core.c |  6 ++++--
 drivers/nvme/target/zns.c  | 17 +++++++++++++++--
 4 files changed, 32 insertions(+), 12 deletions(-)

             reply	other threads:[~2022-09-08 15:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 15:35 Christoph Hellwig [this message]
2022-09-08 16:20 ` [GIT PULL] nvme fixes for Linux 6.0 Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2022-09-29 15:02 Christoph Hellwig
2022-09-29 15:10 ` Jens Axboe
2022-09-01  7:29 Christoph Hellwig
2022-09-01 14:11 ` Jens Axboe
2022-08-11 14:05 Christoph Hellwig
2022-08-11 14:38 ` Jens Axboe

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.