aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/arm-cs-trace-disasm.py
diff options
context:
space:
mode:
authorHåkon Bugge <[email protected]>2025-07-02 09:10:34 +0000
committerYu Kuai <[email protected]>2025-07-05 11:36:50 +0000
commitc17fb542dbd1db745c9feac15617056506dd7195 (patch)
treeaae48e7288e5a7e1c9cadbc00e235ca847c1c027 /tools/perf/scripts/python/arm-cs-trace-disasm.py
parentmd/raid1,raid10: strip REQ_NOWAIT from member bios (diff)
downloadkernel-c17fb542dbd1db745c9feac15617056506dd7195.tar.gz
kernel-c17fb542dbd1db745c9feac15617056506dd7195.zip
md/md-bitmap: fix GPF in bitmap_get_stats()
The commit message of commit 6ec1f0239485 ("md/md-bitmap: fix stats collection for external bitmaps") states: Remove the external bitmap check as the statistics should be available regardless of bitmap storage location. Return -EINVAL only for invalid bitmap with no storage (neither in superblock nor in external file). But, the code does not adhere to the above, as it does only check for a valid super-block for "internal" bitmaps. Hence, we observe: Oops: GPF, probably for non-canonical address 0x1cd66f1f40000028 RIP: 0010:bitmap_get_stats+0x45/0xd0 Call Trace: seq_read_iter+0x2b9/0x46a seq_read+0x12f/0x180 proc_reg_read+0x57/0xb0 vfs_read+0xf6/0x380 ksys_read+0x6d/0xf0 do_syscall_64+0x8c/0x1b0 entry_SYSCALL_64_after_hwframe+0x76/0x7e We fix this by checking the existence of a super-block for both the internal and external case. Fixes: 6ec1f0239485 ("md/md-bitmap: fix stats collection for external bitmaps") Cc: [email protected] Reported-by: Gerald Gibson <[email protected]> Signed-off-by: Håkon Bugge <[email protected]> Link: https://lore.kernel.org/linux-raid/[email protected] Signed-off-by: Yu Kuai <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/arm-cs-trace-disasm.py')
0 files changed, 0 insertions, 0 deletions