summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/task-analyzer.py
diff options
context:
space:
mode:
authorLee Jones <lee@kernel.org>2024-01-11 16:17:26 +0300
committerMartin K. Petersen <martin.petersen@oracle.com>2024-01-30 04:34:52 +0300
commitbc978cc18d46dd54160f6c29aaf9475772686dfc (patch)
treec115532ed99e10048c952786a5a4e8905b7e91ca /tools/perf/scripts/python/task-analyzer.py
parentf615c74de38300f2918033b5c44ac829d1fb7794 (diff)
downloadlinux-bc978cc18d46dd54160f6c29aaf9475772686dfc.tar.xz
scsi: aacraid: aachba: 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: Adaptec OEM Raid Solutions <aacraid@microsemi.com> Cc: PMC-Sierra, Inc <aacraid@pmc-sierra.com> Signed-off-by: Lee Jones <lee@kernel.org> Link: https://lore.kernel.org/r/20240111131732.1815560-6-lee@kernel.org Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions