summaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/tasks.py
diff options
context:
space:
mode:
authorLee Jones <lee@kernel.org>2023-11-30 13:54:36 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2023-12-04 16:25:17 +0300
commitb385ef088c7aab20a2c0dc20d390d69a6620f0f3 (patch)
treeb090475598698b9f887296cb690464090ba648c4 /scripts/gdb/linux/tasks.py
parent36d8aef52d0562b5b1dc2e54d0fad1dee07182c2 (diff)
downloadlinux-b385ef088c7aab20a2c0dc20d390d69a6620f0f3.tar.xz
usb: cdnsp: 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 all seem to assume that data *has been* written! Link: https://lwn.net/Articles/69419/ Link: https://github.com/KSPP/linux/issues/105 Cc: Pawel Laszczak <pawell@cadence.com> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: linux-usb@vger.kernel.org Signed-off-by: Lee Jones <lee@kernel.org> Link: https://lore.kernel.org/r/20231130105459.3208986-3-lee@kernel.org Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'scripts/gdb/linux/tasks.py')
0 files changed, 0 insertions, 0 deletions