diff options
| author | Lee Jones <[email protected]> | 2023-11-30 10:54:37 +0000 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2023-12-04 22:25:17 +0900 |
| commit | 7d7f794482b74e39d8c0cd830333eb40fc0234d4 (patch) | |
| tree | c213aed1a83100e38baacc6566e5159354d6f293 /tools/perf/scripts/python | |
| parent | b385ef088c7aab20a2c0dc20d390d69a6620f0f3 (diff) | |
usb: fotg210-hcd: 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.
The uses in this file both seem to assume that data *has been* written!
Link: https://lwn.net/Articles/69419/
Link: https://github.com/KSPP/linux/issues/105
Cc: Linus Walleij <[email protected]>
Cc: Greg Kroah-Hartman <[email protected]>
Cc: Yuan-Hsin Chen <[email protected]>
Cc: Feng-Hsin Chiang <[email protected]>
Cc: Po-Yu Chuang <[email protected]>
Cc: [email protected]
Signed-off-by: Lee Jones <[email protected]>
Reviewed-by: Linus Walleij <[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