aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/Makefile.thinlto
diff options
context:
space:
mode:
authorMaurizio Lombardi <mlombard@redhat.com>2026-09-08 16:34:34 +0200
committerKeith Busch <kbusch@kernel.org>2026-09-11 07:39:36 -0700
commit62b70e6c87121ae5b79ca20c3a5b005590336ec5 (patch)
treef63ee812f068a63190cbf78f461e0a07f6f24ce4 /scripts/Makefile.thinlto
parentnvme-pci: add NVME_QUIRK_DMAPOOL_ALIGN_512 for Micron 4100AT (diff)
nvme-fc: do not warn on controller removal race
In nvme_fc_reconnect_or_delete(), the system attempts to remove the controller when reconnect limits are reached by calling nvme_delete_ctrl(). This call is currently wrapped in a WARN_ON(). If a user concurrently deletes the controller via sysfs, the controller's state may have already transitioned out of the CONNECTING state. When this happens, nvme_delete_ctrl() correctly rejects the operation and returns -EBUSY. Because of the WARN_ON() wrapper, this race condition triggers an unnecessary kernel warning stack trace. Remove the WARN_ON() macro around nvme_delete_ctrl(); this allows the system to safely ignore the -EBUSY return value if the controller is already being deleted. Signed-off-by: Maurizio Lombardi <mlombard@redhat.com> Reviewed-by: Daniel Wagner <dwagner@suse.de> Signed-off-by: Keith Busch <kbusch@kernel.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions