Hi,
It would be good if this can be merged. The commit from linux-next is
now in Linux mainline tree.
commit: 55c49fee57af99f3c663e69dedc5b85e691bbe50
mm/vmalloc: remove vmap_area_list
Testing this will also require patching makedumpfile with below patch,
otherwise makedumpfile might fail to collect vmcore:
[PATCH] makedumpfile: ppc64: get vmalloc start address from vmcoreinfo
https://lore.kernel.org/kexec/kjitig4jcelchtqria3mmr2jd3h5uptpoeyesif6crnzdtel72@jlit5ntwzdig/T/#t
Any comments ?
Thanks,
- Aditya Gupta
On 01/03/24 16:16, Sachin Sant wrote:
On 01-Mar-2024, at 12:32 PM, Aditya Gupta <[email protected]> wrote:
Below error is noticed when running crash on vmcore collected from a linux-next
kernel crash (linux-next tag next-20240121):
# crash /boot/vmlinuz-6.8.0-rc5-next-20240221 ./vmcore
……
……
For help, type “help”.
Type "apropos word" to search for commands related to "word"...
crash: page excluded: kernel virtual address: c00000000219a2c0 type:
“vmlist"
This occured since getting the vmalloc area base address doesn't work in
crash now, due to 'vmap_area_list' being removed in the linux kernel with
below commit (in linux-next tree):
commit 378eb24a0658dd922b29524e0ce35c6c43f56cba
mm/vmalloc: remove vmap_area_list
As an alternative, the commit introduced 'VMALLOC_START' in vmcoreinfo to
get base address of vmalloc area, use it to return vmallow start address
instead of depending on vmap_area_list and vmlist
Reported-by: Sachin Sant <[email protected]>
Signed-off-by: Aditya Gupta <[email protected]>
---
Thanks Aditya for this fix. With this patch applied, crash is able to
read vmcore generated against kernel that contains
commit 378eb24a0658
Tested-by: Sachin Sant <[email protected]>
— Sachin
--
Crash-utility mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://${domain_name}/admin/lists/devel.lists.crash-utility.osci.io/
Contribution Guidelines: https://github.com/crash-utility/crash/wiki
