summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorLee Jones <lee@kernel.org>2023-12-13 19:42:31 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2023-12-15 15:55:29 +0300
commitc1a371866db9c44ab3004b5fc06df066a1b96262 (patch)
treefe877ddf22593b0282c1a467403e2824c3f76c79 /tools/perf/scripts/python/export-to-postgresql.py
parent0466e7e693efe6647f23532529a9c41a1fa5f4ac (diff)
downloadlinux-c1a371866db9c44ab3004b5fc06df066a1b96262.tar.xz
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 <ruslan.bilovol@gmail.com> Cc: Julian Scheel <julian@jusst.de> Cc: Bryan Wu <cooloney@kernel.org> Signed-off-by: Lee Jones <lee@kernel.org> Link: https://lore.kernel.org/r/20231213164246.1021885-3-lee@kernel.org Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions