Arnd Bergmann 4ee7ffeb4c nvmet: re-fix tracing strncpy() warning ... An earlier patch had tried to address a warning about a string copy with missing zero termination: drivers/nvme/target/trace.h:52:3: warning: ‘strncpy’ specified bound 32 equals destination size [-Wstringop-truncation] The new version causes a different warning with some compiler versions, notably gcc-9 and gcc-10, and also misses the zero padding that was apparently done intentionally in the original code: drivers/nvme/target/trace.h:56:2: error: 'strncpy' specified bound depends on the length of the source argument [-Werror=stringop-overflow=] Change it to use strscpy_pad() with the original length, which will give a properly padded and zero-terminated string as well as avoiding the warning. Fixes: d86481e924 ("nvmet: use min of device_path and disk len") Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Keith Busch <kbusch@kernel.org>		2024-01-05 13:16:18 -08:00
..
common	nvme-common: mark nvme_tls_psk_prio static	2024-01-03 08:09:40 -08:00
host	nvme: introduce nvme_disk_is_ns_head helper	2024-01-05 13:15:41 -08:00
target	nvmet: re-fix tracing strncpy() warning	2024-01-05 13:16:18 -08: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