diff options
author | Justin Stitt <[email protected]> | 2023-10-03 22:23:07 +0000 |
---|---|---|
committer | Greg Kroah-Hartman <[email protected]> | 2023-10-05 13:34:04 +0200 |
commit | 14388ec0052c14640bf805dee55372f92557c6d9 (patch) | |
tree | 8531814bb256cc254d2b5873c30ab3a997a44555 /tools/perf/scripts/python/mem-phys-addr.py | |
parent | 2801badd26540ecc9c93f6007e2d6e5030246d76 (diff) |
drivers: misc: ti-st: replace deprecated strncpy with strscpy
`strncpy` is deprecated for use on NUL-terminated destination strings
[1] and as such we should prefer more robust and less ambiguous string
interfaces.
We expect both `kim_data->dev_name` and `kim_gdata->dev_name` to be
NUL-terminated.
`kim_data->dev_name` seems to not require NUL-padding.
`kim_gdata` is already zero-allocated and as such does not require
NUL-padding:
| kim_gdata = kzalloc(sizeof(struct kim_data_s), GFP_KERNEL);
Considering the above, a suitable replacement is `strscpy` [2] due to
the fact that it guarantees NUL-termination on the destination buffer
without unnecessarily NUL-padding.
Let's also opt to use the more idiomatic strscpy usage of:
strscpy(dest, src, sizeof(dest))
Link: https://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
Cc: [email protected]
Signed-off-by: Justin Stitt <[email protected]>
Reviewed-by: Kees Cook <[email protected]>
Link: https://lore.kernel.org/r/20231003-strncpy-drivers-misc-ti-st-st_kim-c-v2-1-79630447b0a1@google.com
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions