All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me
Subject: Re: [GIT PULL] nvme updates for Linux 7.4
Date: Thu, 29 Oct 2026 09:33:37 -0600	[thread overview]
Message-ID: <512bb09c-2d14-4f20-8508-dacb59a30e2f@kernel.dk> (raw)
In-Reply-To: <auNZdZx2COp-NCyI@kbusch-mbp>

On 10/29/26 8:34 AM, Keith Busch wrote:
> ----------------------------------------------------------------
> nvme updates for Linux 7.4
> 
>  - Fix regressions from the parallel nvme-tcp I/O queue setup: request
>    PDU sizing with header digest, a NULL controller dereference when
>    reconnecting with more queues, and early lock initialization
>  - Handle TLS control records in nvme-tcp: skip records arriving ahead
>    of the ICResp, and start error recovery when the socket read fails
>  - Fix an nvme-tcp io_work priority inversion stalling I/O
>  - Fix nvme-tcp address attribute race with queue teardown
>  - Validate the TLS handshake timeout parameters for host and target
>  - Fix fabrics connects with isolated CPUs and queue mapping bugs
>  - Fix early boot hang and buffer size for the nvme.quirks parameter
>  - Fix nvme-rdma NULL metadata SGL dereference with T10-PI
>  - Fix ANA underflow check and an nvme-fc discovery reference leak
>  - Fix nvme-loop BUG() when a namespace scan races a reset
>  - Target port and configfs locking fixes, and port removal races
>  - Target auth fixes for CHALLENGE failure and negotiation handling
>  - Target fc fixes for a connection use-after-free, read data on failed
>    commands, and admin queue allocation failure teardown
>  - Target rdma fix for short connection requests
>  - Target rdma fix for inline SGL out-of-bounds write
>  - Target rdma refcount, locking, and module unload fixes
>  - Target pci-epf SGL length and error status fixes
>  - Target NULL dereference fixes for pci-epf and debugfs
>  - Target ZNS NUMD overflow check
>  - Target Connect fix for a controller leak with a zero queue size
>  - Target fixes for a metadata SGL double-free and a leaked blk plug
>  - Target fix for truncated large discards
>  - Misc cleanups

Pulled, thanks.

-- 
Jens Axboe


  parent reply	other threads:[~2026-10-29 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 14:34 [GIT PULL] nvme updates for Linux 7.4 Keith Busch
2026-10-29 14:56 ` Keith Busch
2026-10-29 15:33 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-10-15 20:51 Keith Busch
2026-10-15 22:35 ` 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=512bb09c-2d14-4f20-8508-dacb59a30e2f@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --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.