diff options
author | Justin Stitt <justinstitt@google.com> | 2023-08-07 18:22:30 +0000 |
---|---|---|
committer | Richard Weinberger <richard@nod.at> | 2023-08-26 22:42:50 +0200 |
commit | e30955d029a8834c93c9bd0226fa6c1dfc59c812 (patch) | |
tree | e49544643e85a915960d9c4b1f4262e5b2fea12b /rust | |
parent | 8f85f93bfd2d490251143577bd43b01b40acb8d7 (diff) | |
download | linux-stable-e30955d029a8834c93c9bd0226fa6c1dfc59c812.tar.gz linux-stable-e30955d029a8834c93c9bd0226fa6c1dfc59c812.tar.bz2 linux-stable-e30955d029a8834c93c9bd0226fa6c1dfc59c812.zip |
um: vector: refactor deprecated strncpy
`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, we are able to drop the now superfluous `... - 1`
instances because `strscpy` will automatically truncate the last byte by
setting it to a NUL byte if the source size exceeds the destination size
or if the source string is not NUL-terminated.
I've also opted to remove the seemingly useless char* casts. I'm not
sure why they're present at all since (after expanding the `ifr_name`
macro) `ifr.ifr_ifrn.ifrn_name` is a char* already.
All in all, `strscpy` is a more robust and less ambiguous interface
while also letting us remove some `... -1`'s which cleans things up a
bit.
[1]: www.kernel.org/doc/html/latest/process/deprecated.html#strncpy-on-nul-terminated-strings
[2]: https://manpages.debian.org/testing/linux-manual-4.8/strscpy.9.en.html
Link: https://github.com/KSPP/linux/issues/90
Cc: linux-hardening@vger.kernel.org
Signed-off-by: Justin Stitt <justinstitt@google.com>
Acked-by: Anton Ivanov <anton.ivanov@cambridgegreys.com>
Signed-off-by: Richard Weinberger <richard@nod.at>
Diffstat (limited to 'rust')
0 files changed, 0 insertions, 0 deletions