On Thu, Sep 22, 2016 at 1:41 AM, Dave Young wrote:
> Hi, Thomas
>
> On 08/17/16 at 09:47am, Thomas Garnier wrote:
>> Multiple changes were made on KASLR (right now in linux-next). One of
>> them is randomizing the virtual address of the physical mapping, vmalloc
>> and vmemmap
>Hello,
>
>I am investigating an issue with makedumpfile and kernel 4.8 where makedumpfile
>(1.6.0) exits on error with the following message :
>
> get_mem_map: Can't distinguish the memory type.
>
>I found commit 2c21d4656e8d3c2af2b1e14809d076941ae69e96 in the upstream
>development branch that
On 23/09/2016:12:47:39 PM, Madhavan Srinivasan wrote:
> In dt_copy_old_root_param(), FILE * returned
> from fopen is not checked for NULL pointer
> before passinig to fclose(). This could trigger
> a segfault. Patch adds a check.
>
> Signed-off-by: Madhavan Srinivasan
>
Hi Geoff,
On 21/09/2016:06:14:25 PM, Geoff Levand wrote:
> This series adds the core support for kexec re-boot on ARM64.
I tested this series with mustang and seattle and they work.
So you can use my "Tested-By: Pratyush Anand ".
Just one Nitpick: In patch 2/3
On Thu, Sep 22, 2016 at 12:23:08PM +0200, Matthias Bruger wrote:
>
>
> On 09/07/2016 06:29 AM, AKASHI Takahiro wrote:
> >On the startup of primary kernel, the memory region used by crash dump
> >kernel must be specified by "crashkernel=" kernel parameter.
> >reserve_crashkernel() will allocate
On 09/23/16 at 12:47pm, Madhavan Srinivasan wrote:
> In dt_copy_old_root_param(), FILE * returned
> from fopen is not checked for NULL pointer
> before passinig to fclose(). This could trigger
> a segfault. Patch adds a check.
>
> Signed-off-by: Madhavan Srinivasan
>