diff options
| author | Lee Jones <[email protected]> | 2023-12-13 16:42:31 +0000 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2023-12-15 13:55:29 +0100 |
| commit | c1a371866db9c44ab3004b5fc06df066a1b96262 (patch) | |
| tree | fe877ddf22593b0282c1a467403e2824c3f76c79 /tools/perf/scripts/python | |
| parent | 0466e7e693efe6647f23532529a9c41a1fa5f4ac (diff) | |
usb: gadget: f_uac1: 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: Ruslan Bilovol <[email protected]>
Cc: Julian Scheel <[email protected]>
Cc: Bryan Wu <[email protected]>
Signed-off-by: Lee Jones <[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