aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/flamegraph.py
diff options
context:
space:
mode:
authorMikulas Patocka <[email protected]>2023-01-22 14:02:57 -0500
committerMike Snitzer <[email protected]>2023-02-01 11:35:30 -0500
commitf50714b57aecb6b3dc81d578e295f86d9c73f078 (patch)
treec5a886cf224f8a50440b6efe92d6b8323c73971b /tools/perf/scripts/python/flamegraph.py
parent22c40e134c4c7a828ac09d25a5a8597b1e45c031 (diff)
dm flakey: don't corrupt the zero page
When we need to zero some range on a block device, the function __blkdev_issue_zero_pages submits a write bio with the bio vector pointing to the zero page. If we use dm-flakey with corrupt bio writes option, it will corrupt the content of the zero page which results in crashes of various userspace programs. Glibc assumes that memory returned by mmap is zeroed and it uses it for calloc implementation; if the newly mapped memory is not zeroed, calloc will return non-zeroed memory. Fix this bug by testing if the page is equal to ZERO_PAGE(0) and avoiding the corruption in this case. Cc: [email protected] Fixes: a00f5276e266 ("dm flakey: Properly corrupt multi-page bios.") Signed-off-by: Mikulas Patocka <[email protected]> Reviewed-by: Sweet Tea Dorminy <[email protected]> Signed-off-by: Mike Snitzer <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions