[Crash-utility] [PATCH 0/1] arm64: Fix missing offset for modules_vaddr with aarch64 guest dump

Dave Anderson anderson at redhat.com
Mon Jan 27 14:56:53 UTC 2020



----- Original Message -----
> From: Masayoshi Mizuma <m.mizuma at jp.fujitsu.com>
> 
> Fix for aarch64 with Linux v5.0 and later kernels that
> contains commit 91fc957c9b1d ("arm64/bpf: don't allocate
> BPF JIT programs in module memory") and the memory dump
> is captured by virsh dump.
> 
> Note: Another two issues remain for the memory dump captured by
> virsh dump with aarch64.

I'm confused -- the vmcoreinfo data has been passed to the KVM host
for the virsh dump for quite some time now.  Is it not passed back
to the host on aarch64?

Dave

  I
> 
> 1. KASLR
>    crash doesn't work in case KASLR is enabled on the guest.
>    That is because the memory dump doesn't have vmcoreinfo, so we
>    cannot get the relocation position.
>    I suppose we need to implement calc_kaslr_offset() for aarch64.
>    nokaslr with the guest kernel parameter is a workaround.
> 
> 2. VA_BITS
>    crash doesn't work in case the guest kernel is v5.4 and later.
>    That is because the memory dump doesn't have vmcoreinfo, so we
>    cannot get vabits_actual.
>    I think there's no workaround so far...
> 
> Masayoshi Mizuma (1):
>   arm64: Fix missing offset for modules_vaddr with aarch64 guest dump
> 
>  arm64.c | 2 ++
>  defs.h  | 3 +++
>  2 files changed, 5 insertions(+)
> 
> --
> 2.18.1
> 
> 
> --
> Crash-utility mailing list
> Crash-utility at redhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility
> 




More information about the Crash-utility mailing list