From: Keith Busch <kbusch@kernel.org>
To: axboe@kernel.dk
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me
Subject: [GIT PULL] nvme fixes for Linux 6.14
Date: Thu, 20 Feb 2025 17:07:24 -0700 [thread overview]
Message-ID: <Z7fDvDmMihwtyUDV@kbusch-mbp> (raw)
The following changes since commit dd8b0582e25e36bba483c60338741c0ba5bc426c:
block: fix NULL pointer dereferenced within __blk_rq_map_sg (2025-02-17 09:04:07 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-6.14-2025-02-20
for you to fetch changes up to d2fe192348f93fe3a0cb1e33e4aba58e646397f4:
nvme: only allow entering LIVE from CONNECTING state (2025-02-20 09:14:25 -0800)
----------------------------------------------------------------
nvme fixes for Linux 6.14
- FC controller state check fixes (Daniel)
- PCI Endpoint fixes (Damien)
- TCP connection failure fix (Caleb)
- TCP handling C2HTermReq PDU (Maurizio)
- RDMA queue state check (Ruozhu)
- Apple controller fixes (Hector)
- Target crash on disbaled namespace (Hannes)
----------------------------------------------------------------
Caleb Sander Mateos (2):
nvme-tcp: fix connect failure on receiving partial ICResp PDU
nvme/ioctl: add missing space in err message
Christopher Lentocha (1):
nvme-pci: quirk Acer FA100 for non-uniqueue identifiers
Damien Le Moal (6):
nvmet: pci-epf: Correctly initialize CSTS when enabling the controller
nvmet: pci-epf: Do not uselessly write the CSTS register
nvmet: pci-epf: Avoid RCU stalls under heavy workload
nvme: tcp: Fix compilation warning with W=1
nvme: Cleanup the definition of the controller config register fields
nvmet: Use enum definitions instead of hardcoded values
Daniel Wagner (2):
nvme-fc: rely on state transitions to handle connectivity loss
nvme: only allow entering LIVE from CONNECTING state
Hannes Reinecke (1):
nvmet: Fix crash when a namespace is disabled
Hector Martin (2):
apple-nvme: Release power domains when probe fails
apple-nvme: Support coprocessors left idle
Maurizio Lombardi (1):
nvme-tcp: add basic support for the C2HTermReq PDU
Ruozhu Li (1):
nvmet-rdma: recheck queue state is LIVE in state lock in recv done
drivers/nvme/host/apple.c | 55 ++++++++++++++++++++++++-----------
drivers/nvme/host/core.c | 2 --
drivers/nvme/host/fc.c | 67 ++++---------------------------------------
drivers/nvme/host/ioctl.c | 3 +-
drivers/nvme/host/pci.c | 2 ++
drivers/nvme/host/tcp.c | 50 ++++++++++++++++++++++++++++++--
drivers/nvme/target/core.c | 40 ++++++++++++--------------
drivers/nvme/target/nvmet.h | 14 ++++-----
drivers/nvme/target/pci-epf.c | 39 ++++++++++++++++++-------
drivers/nvme/target/rdma.c | 33 ++++++++++++++-------
include/linux/nvme-tcp.h | 2 ++
include/linux/nvme.h | 40 +++++++++++++++++++++-----
12 files changed, 208 insertions(+), 139 deletions(-)
next reply other threads:[~2025-02-21 0:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 0:07 Keith Busch [this message]
2025-02-21 0:45 ` [GIT PULL] nvme fixes for Linux 6.14 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2025-03-13 15:31 Keith Busch
2025-03-13 15:42 ` Jens Axboe
2025-03-06 1:39 Keith Busch
2025-03-06 11:33 ` Jens Axboe
2025-02-03 15:03 Keith Busch
2025-02-03 16:19 ` 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:
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=Z7fDvDmMihwtyUDV@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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 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.