diff options
author | 2024-01-11 13:17:26 +0000 | |
---|---|---|
committer | 2024-01-29 20:34:52 -0500 | |
commit | bc978cc18d46dd54160f6c29aaf9475772686dfc (patch) | |
tree | c115532ed99e10048c952786a5a4e8905b7e91ca /scripts/generate_rust_analyzer.py | |
parent | scsi: 53c700: Remove snprintf() from sysfs call-backs and replace with sysfs_emit() (diff) | |
download | linux-rng-bc978cc18d46dd54160f6c29aaf9475772686dfc.tar.xz linux-rng-bc978cc18d46dd54160f6c29aaf9475772686dfc.zip |
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 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions