public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: [GIT PULL] Block fixes for 6.10-rc4
Date: Fri, 14 Jun 2024 10:10:38 -0600	[thread overview]
Message-ID: <2392bf6b-f048-4a80-a9b2-8703ead1fa10@kernel.dk> (raw)

Hi Linus,

Fixes for block that should go into the 6.10 kernel release:

- NVMe pull request via Keith
	- Discard double free on error conditions (Chunguang)
	- Target Fixes (Daniel)
	- Namespace detachment regression fix (Keith)

- Fix for an issue with flush requests and queuelist reuse (Chengming)

- nbd sparse annotation fixes (Christoph)

- unmap and free bio mapped data via submitter (Anuj)

- loop discard/fallocate unsupported fix (Cyril)

- Fix for the zoned write plugging added in this release (Damien)

- sed-opal wrong address fix (Su)

Please pull!


The following changes since commit 27d024235bdb16af917809d33916392452c3ac85:

  Merge tag 'nvme-6.10-2024-06-05' of git://git.infradead.org/nvme into block-6.10 (2024-06-05 12:13:00 -0600)

are available in the Git repository at:

  git://git.kernel.dk/linux.git tags/block-6.10-20240614

for you to fetch changes up to 5f75e081ab5cbfbe7aca2112a802e69576ee9778:

  loop: Disable fallocate() zero and discard if not supported (2024-06-14 06:21:25 -0600)

----------------------------------------------------------------
block-6.10-20240614

----------------------------------------------------------------
Anuj Gupta (1):
      block: unmap and free user mapped integrity via submitter

Chengming Zhou (1):
      block: fix request.queuelist usage in flush

Christoph Hellwig (1):
      nbd: Remove __force casts

Chunguang Xu (1):
      nvme: avoid double free special payload

Cyril Hrubis (1):
      loop: Disable fallocate() zero and discard if not supported

Damien Le Moal (1):
      block: Optimize disk zone resource cleanup

Daniel Wagner (2):
      nvmet-passthru: propagate status from id override functions
      nvmet: always initialize cqe.result

Jens Axboe (1):
      Merge tag 'nvme-6.10-2024-06-13' of git://git.infradead.org/nvme into block-6.10

Keith Busch (1):
      nvme: fix namespace removal list

Su Hui (1):
      block: sed-opal: avoid possible wrong address reference in read_sed_opal_key()

 block/bio-integrity.c                  | 26 +++++++++++++++--
 block/blk-flush.c                      |  3 +-
 block/blk-zoned.c                      |  3 ++
 block/sed-opal.c                       |  2 +-
 drivers/block/loop.c                   | 23 +++++++++++++++
 drivers/block/nbd.c                    | 51 +++++++++++++++-------------------
 drivers/nvme/host/core.c               | 10 ++++---
 drivers/nvme/host/ioctl.c              | 15 +++++++---
 drivers/nvme/target/core.c             |  1 +
 drivers/nvme/target/fabrics-cmd-auth.c |  3 --
 drivers/nvme/target/fabrics-cmd.c      |  6 ----
 drivers/nvme/target/passthru.c         |  6 ++--
 include/linux/bio.h                    |  4 +++
 13 files changed, 100 insertions(+), 53 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2024-06-14 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14 16:10 Jens Axboe [this message]
2024-06-14 18:52 ` [GIT PULL] Block fixes for 6.10-rc4 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=2392bf6b-f048-4a80-a9b2-8703ead1fa10@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@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