summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorZHOU Jiaxiang <me@fxti.xyz>2026-09-16 21:58:21 +0800
committerMartin K. Petersen (Oracle) <mkp@kernel.org>2026-09-16 10:11:45 -0400
commit7c431d61b69a3fd0784c20aa4cd0b8fb501b5653 (patch)
tree03ea9189ea25b8c6dcc470adf6a6cface1036195 /tools/perf/scripts/python/stackcollapse.py
parent278210c60c6f6958bd2eeaa2120c862683b83d09 (diff)
downloadlinux-next-7c431d61b69a3fd0784c20aa4cd0b8fb501b5653.tar.gz
linux-next-7c431d61b69a3fd0784c20aa4cd0b8fb501b5653.zip
scsi: block: Fix zones_cond out-of-bounds write on zone report
blk_revalidate_disk_zones() sizes the zones_cond array from the disk capacity and zone size, but the index used by blk_revalidate_zone_cond() comes from the device-driven report_zones() walk and is never checked against the array size. A device reporting more zones than fit the array makes blk_zone_set_cond() write out of bounds. One way to reach this is a zone count exceeding 32 bits: both blk_revalidate_zone_args.nr_zones and struct zoned_disk_info.nr_zones are unsigned int, so a disk advertising more than UINT_MAX zones (e.g. 2^32 + 1024 zones of one 512-byte logical block) gets its zone count truncated to a small value, undersizing the array while the report walk keeps counting upward. Check the index against the array size before storing the zone condition, and refuse to revalidate when the zone count does not fit 32 bits. Fixes: 6e945ffb6555 ("block: use zone condition to determine conventional zones") Signed-off-by: ZHOU Jiaxiang <me@fxti.xyz> Reviewed-by: Damien Le Moal <dlemoal@kernel.org> Link: https://patch.msgid.link/7815D1B293A8F55E+20260916135822.32584-2-me@fxti.xyz Signed-off-by: Martin K. Petersen (Oracle) <mkp@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions