diff options
author | Lee Jones <[email protected]> | 2023-12-13 16:42:33 +0000 |
---|---|---|
committer | Greg Kroah-Hartman <[email protected]> | 2023-12-15 13:55:29 +0100 |
commit | 0d12c1cca7883620b1888ce4b892a9ed27bf3682 (patch) | |
tree | 64a6e6454794e02e9d439319c87947fa04d4146b /tools/perf/scripts/python | |
parent | 60034e0aedf507888c4a880f57011bb7f5d7700c (diff) |
usb: gadget: uvc: Replace snprintf() with the safer scnprintf() variant
There is a general misunderstanding amongst engineers that {v}snprintf()
returns the length of the data *actually* encoded into the destination
array. However, as per the C99 standard {v}snprintf() really returns
the length of the data that *would have been* written if there were
enough space for it. This misunderstanding has led to buffer-overruns
in the past. It's generally considered safer to use the {v}scnprintf()
variants in their place (or even sprintf() in simple cases). So let's
do that.
Link: https://lwn.net/Articles/69419/
Link: https://github.com/KSPP/linux/issues/105
Cc: Laurent Pinchart <[email protected]>
Cc: Daniel Scally <[email protected]>
Cc: Andrzej Pietrasiewicz <[email protected]>
Signed-off-by: Lee Jones <[email protected]>
Reviewed-by: Laurent Pinchart <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions