Re: [Crash-utility] [PATH v4 1/2] arm64: fix kernel memory map handling for kaslr-enabled kernel

2016-06-03 Thread Dave Anderson
- Original Message - > > The VMCOREINFO is primarily there for the user-space kdump and makedumpfile > > facilities. Crash does check it occasionally, but can't depend upon it, > > because there are too many other dumpfile formats. > > That is the reason that I insist on minimizing the

Re: [Crash-utility] [PATH v4 1/2] arm64: fix kernel memory map handling for kaslr-enabled kernel

2016-06-02 Thread AKASHI Takahiro
On Thu, Jun 02, 2016 at 11:37:24AM -0400, Dave Anderson wrote: > - Original Message - > > On Wed, Jun 01, 2016 at 11:41:04AM -0400, Dave Anderson wrote: > > > > > > - Original Message - > > > > > > > > > > > > > > > case PRE_GDB: > > > > > > + /* This check is some

Re: [Crash-utility] [PATH v4 1/2] arm64: fix kernel memory map handling for kaslr-enabled kernel

2016-06-02 Thread Dave Anderson
- Original Message - > On Wed, Jun 01, 2016 at 11:41:04AM -0400, Dave Anderson wrote: > > > > - Original Message - > > > > > > > > > > > > case PRE_GDB: > > > > > + /* This check is somewhat redundant */ > > > > > + if (kernel_symbol_exists("kimage_

Re: [Crash-utility] [PATH v4 1/2] arm64: fix kernel memory map handling for kaslr-enabled kernel

2016-06-01 Thread AKASHI Takahiro
On Wed, Jun 01, 2016 at 11:41:04AM -0400, Dave Anderson wrote: > > - Original Message - > > > > > > > > > case PRE_GDB: > > > > + /* This check is somewhat redundant */ > > > > + if (kernel_symbol_exists("kimage_voffset")) > > > > +

Re: [Crash-utility] [PATH v4 1/2] arm64: fix kernel memory map handling for kaslr-enabled kernel

2016-06-01 Thread Dave Anderson
- Original Message - > > > > > > case PRE_GDB: > > > + /* This check is somewhat redundant */ > > > + if (kernel_symbol_exists("kimage_voffset")) > > > + machdep->flags |= NEW_VMEMMAP; > > > + > > > > Certainly not redundant on a live system without C

Re: [Crash-utility] [PATH v4 1/2] arm64: fix kernel memory map handling for kaslr-enabled kernel

2016-06-01 Thread AKASHI Takahiro
On Tue, May 31, 2016 at 03:29:01PM -0400, Dave Anderson wrote: > > - Original Message - > > In kernel v4.6, Kernel ASLR (KASLR) is supported on arm64, and the start > > address of the kernel image can be randomized if CONFIG_RANDOMIZE_BASE is > > enabled. > > Even worse, the kernel image

Re: [Crash-utility] [PATH v4 1/2] arm64: fix kernel memory map handling for kaslr-enabled kernel

2016-05-31 Thread Dave Anderson
- Original Message - > In kernel v4.6, Kernel ASLR (KASLR) is supported on arm64, and the start > address of the kernel image can be randomized if CONFIG_RANDOMIZE_BASE is > enabled. > Even worse, the kernel image is no more mapped in the linear mapping, but > in vmalloc area (i.e. belo

Re: [Crash-utility] [PATH v4 1/2] arm64: fix kernel memory map handling for kaslr-enabled kernel

2016-05-30 Thread Pratyush Anand
On 30/05/2016:03:46:07 PM, AKASHI Takahiro wrote: > In kernel v4.6, Kernel ASLR (KASLR) is supported on arm64, and the start > address of the kernel image can be randomized if CONFIG_RANDOMIZE_BASE is > enabled. > Even worse, the kernel image is no more mapped in the linear mapping, but > in vmallo

[Crash-utility] [PATH v4 1/2] arm64: fix kernel memory map handling for kaslr-enabled kernel

2016-05-29 Thread AKASHI Takahiro
In kernel v4.6, Kernel ASLR (KASLR) is supported on arm64, and the start address of the kernel image can be randomized if CONFIG_RANDOMIZE_BASE is enabled. Even worse, the kernel image is no more mapped in the linear mapping, but in vmalloc area (i.e. below PAGE_OFFSET). Now, according to the kern