diff options
author | Lee Jones <[email protected]> | 2023-12-13 16:42:39 +0000 |
---|---|---|
committer | Greg Kroah-Hartman <[email protected]> | 2023-12-15 13:55:30 +0100 |
commit | 9d4e3d15d7bf3439a6f3fb4aafc4f92ea2c5c5fd (patch) | |
tree | 36dd7903bdd054f93385b28c5aa0b6d3e96f1eb5 /tools/perf/scripts/python/export-to-sqlite.py | |
parent | 79632569619f4d57ff745398dba98e09105b5108 (diff) |
usb: mon_text: 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
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/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions