Re: [PATCH v5 13/17] crash: Assert device_hotplug_lock in crash_get_memory_ranges_nolock()
From: sashiko-bot@kernel.org
Date: 2026-09-18 10:26:47
Also in:
driver-core, kexec, linux-fsdevel, lkml, loongarch
crash_get_memory_ranges_nolock() walks memblock, which memory hotplug modifies under device_hotplug_lock. A caller that does not hold the lock can race with memblock_double_array() and iterate a freed regions array. Add device_hotplug_lock_assert_held() and call it at the top of the function so that such callers are caught by lockdep. Signed-off-by: Jinjie Ruan <redacted>
Sashiko has reviewed this patch and found no issues. It looks great! -- Sashiko AI review · https://sashiko.dev/#/patchset/20260918100442.3841135-1-ruanjinjie@huawei.com?part=13