Linux block layer
 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] 2nd set of block fixes for 6.15-rc2
Date: Fri, 11 Apr 2025 09:07:31 -0600	[thread overview]
Message-ID: <8d3e5d98-09b1-4274-af25-124c91342b7a@kernel.dk> (raw)

Hi Linus,

Apparently my internal clock was off, or perhaps it was just wishful
thinking, but I sent out block fixes yesterday as my brain assumed it
was Friday. Subsequently, that missed the NVMe fixes that should go into
this weeks release as well. Hence, here's a followup with those, and
another simple fix.

This pull request contains:

- NVMe pull request via Christoph
	- nvmet fc/fcloop refcounting fixes (Daniel Wagner)
	- fix missed namespace/ANA scans (Hannes Reinecke)
	- fix a use after free in the new TCP netns support
	  (Kuniyuki Iwashima)
	- fix a NULL instead of false review in multipath (Uday Shankar)

- Use strscpy() for null_blk disk name copy

Please pull!


The following changes since commit 843c6cec1af85f05971b7baf3704801895e77d76:

  ublk: pass ublksrv_ctrl_cmd * instead of io_uring_cmd * (2025-04-09 07:58:04 -0600)

are available in the Git repository at:

  git://git.kernel.dk/linux.git tags/block-6.15-20250411

for you to fetch changes up to 3b607b75a345b1d808031bf1bb1038e4dac8d521:

  null_blk: Use strscpy() instead of strscpy_pad() in null_add_dev() (2025-04-11 07:10:46 -0600)

----------------------------------------------------------------
block-6.15-20250411

----------------------------------------------------------------
Daniel Wagner (8):
      nvmet-fcloop: swap list_add_tail arguments
      nvmet-fcloop: replace kref with refcount
      nvmet-fcloop: add ref counting to lport
      nvmet-fc: inline nvmet_fc_delete_assoc
      nvmet-fc: inline nvmet_fc_free_hostport
      nvmet-fc: update tgtport ref per assoc
      nvmet-fc: take tgtport reference only once
      nvmet-fc: put ref when assoc->del_work is already scheduled

Hannes Reinecke (2):
      nvme: requeue namespace scan on missed AENs
      nvme: re-read ANA log page after ns scan completes

Jens Axboe (1):
      Merge tag 'nvme-6.15-2025-04-10' of git://git.infradead.org/nvme into block-6.15

Kuniyuki Iwashima (1):
      nvme-tcp: fix use-after-free of netns by kernel TCP socket.

Thorsten Blum (1):
      null_blk: Use strscpy() instead of strscpy_pad() in null_add_dev()

Uday Shankar (1):
      nvme: multipath: fix return value of nvme_available_path

 drivers/block/null_blk/main.c |  2 +-
 drivers/nvme/host/core.c      |  9 ++++++
 drivers/nvme/host/multipath.c |  2 +-
 drivers/nvme/host/tcp.c       |  2 ++
 drivers/nvme/target/fc.c      | 60 ++++++++++++-----------------------
 drivers/nvme/target/fcloop.c  | 74 +++++++++++++++++++++++--------------------
 6 files changed, 73 insertions(+), 76 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2025-04-11 15:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11 15:07 Jens Axboe [this message]
2025-04-11 15:40 ` [GIT PULL] 2nd set of block fixes for 6.15-rc2 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=8d3e5d98-09b1-4274-af25-124c91342b7a@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