(subset) [PATCH v2 0/5] nvme: fabrics and target fixes
Keith Busch
kbusch at kernel.org
Mon Nov 9 09:47:13 PST 2026
On Mon, 9 Nov 2026 10:26:41 +0800, Guixin Liu wrote:
> Five fixes found by code inspection of the nvme host and target
> drivers:
>
> - a reconnect_delay of 0 is accepted through sysfs and makes the
> ctrl_loss_tmo store divide by zero; reproduced on an unfixed
> kernel, rejected on the patched one
> - a use-after-free in nvme_fc_match_disconn_ls(): no iterator is
> sound across the rport lock drop inside the loop, so the loop is
> reworked to run entirely under the rport lock and to take a
> reference only for the match; reproduced under KASAN through fcloop
> - a data race on ctrl->transaction between concurrent per-queue
> DH-HMAC-CHAP exchanges
> - nvmet_subsys_attr_tbkas_store() walks subsys->ctrls without
> subsys->lock, the same bug fixed for qid_max_store() in patch 4
> of this series
> - needless GFP_ATOMIC allocations in the nvmet persistent reservation
> code
>
> [...]
Thanks, applied to nvme-7.4.
[5/5] nvmet: use GFP_KERNEL for PR allocations
commit: 976311c5594a7a26047891f087ad59a804e02baa
--
Keith Busch <kbusch at kernel.org>
More information about the Linux-nvme
mailing list