Nilay Shroff 863fe60ed2 nvme: find numa distance only if controller has valid numa id ... On system where native nvme multipath is configured and iopolicy is set to numa but the nvme controller numa node id is undefined or -1 (NUMA_NO_NODE) then avoid calculating node distance for finding optimal io path. In such case we may access numa distance table with invalid index and that may potentially refer to incorrect memory. So this patch ensures that if the nvme controller numa node id is -1 then instead of calculating node distance for finding optimal io path, we set the numa node distance of such controller to default 10 (LOCAL_DISTANCE). Link: https://lore.kernel.org/all/20240413090614.678353-1-nilay@linux.ibm.com/ Signed-off-by: Nilay Shroff <nilay@linux.ibm.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Sagi Grimberg <sagi@grimberg.me> Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com> Signed-off-by: Keith Busch <kbusch@kernel.org>		2024-05-01 02:58:42 -07:00
..
common	nvme-common: add module description	2024-01-31 16:03:49 -08:00
host	nvme: find numa distance only if controller has valid numa id	2024-05-01 02:58:42 -07:00
target	nvmet-fc: move RCU read lock to nvmet_fc_assoc_exists	2024-04-04 08:47:56 -07:00
Kconfig	nvme: implement In-Band authentication	2022-08-02 17:14:49 -06:00
Makefile	nvme: common: make keyring and auth separate modules	2023-11-07 10:05:15 -08:00