summaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorJustin Stitt <justinstitt@google.com>2023-08-23 00:13:36 +0200
committerIngo Molnar <mingo@kernel.org>2023-08-24 21:22:40 +0200
commit4108d141bfd04cf7b2bbf96e899ee5392f62e8a2 (patch)
tree304e91a157ed5a06e6d869cd43b27383b6ae03fa /drivers
parentx86/platform/uv: Refactor code using deprecated strcpy()/strncpy() interfaces... (diff)
downloadlinux-4108d141bfd04cf7b2bbf96e899ee5392f62e8a2.tar.xz
linux-4108d141bfd04cf7b2bbf96e899ee5392f62e8a2.zip
x86/hpet: Refactor code using deprecated strncpy() interface to use strscpy()
`strncpy` is deprecated for use on NUL-terminated destination strings [1]. A suitable replacement is `strscpy` [2] due to the fact that it guarantees NUL-termination on its destination buffer argument which is _not_ the case for `strncpy`! In this case, it is a simple swap from `strncpy` to `strscpy`. There is one slight difference, though. If NUL-padding is a functional requirement here we should opt for `strscpy_pad`. It seems like this shouldn't be needed as I see no obvious signs of any padding being required. Signed-off-by: Justin Stitt <justinstitt@google.com> Signed-off-by: Ingo Molnar <mingo@kernel.org> Link: www.kernel.org/doc/html/latest/process/deprecated.html#strncpy-on-nul-terminated-strings[1] Link: https://manpages.debian.org/testing/linux-manual-4.8/strscpy.9.en.html [2] Link: https://github.com/KSPP/linux/issues/90 Link: https://lore.kernel.org/r/20230822-strncpy-arch-x86-kernel-hpet-v1-1-2c7d3be86f4a@google.com
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions