Hi Dave,
On Tue, Oct 23, 2018 at 7:01 AM Dave Young wrote:
>
> Hi Bhupesh,
>
> On 10/23/18 at 01:50am, Bhupesh Sharma wrote:
> > For calculating the random 'kaslr-seed' value to be passed to the
> > secondary kernel (kexec or kdump), we invoke the 'getrandom' syscall
> > inside 'setup_2nd_dtb()'
Hi Bhupesh,
On 10/23/18 at 01:50am, Bhupesh Sharma wrote:
> For calculating the random 'kaslr-seed' value to be passed to the
> secondary kernel (kexec or kdump), we invoke the 'getrandom' syscall
> inside 'setup_2nd_dtb()' function.
>
> Normally on most arm64 systems this syscall doesn't fail
On 18/10/2018 19:15, Bjorn Helgaas wrote:
> On Thu, Oct 18, 2018 at 03:37:19PM -0300, Guilherme G. Piccoli wrote:
> [...]
> I don't want to expand the early quirk infrastructure unless there is
> absolutely no other way to solve this. The early quirk stuff is
> x86-specific, and it's not
For calculating the random 'kaslr-seed' value to be passed to the
secondary kernel (kexec or kdump), we invoke the 'getrandom' syscall
inside 'setup_2nd_dtb()' function.
Normally on most arm64 systems this syscall doesn't fail when the
initrd scriptware (which arms kdump service) invokes the
On 18/10/2018 17:30, Sinan Kaya wrote:
>
> AFAIK, all shutdown (not remove) routines are called before launching
> the next
> kernel even in crash scenario. It is not safe to start the new kernel while
> hardware is doing a DMA to the system memory and triggering interrupts.
Hi Sinan,
I agree
If the err_out label is reached, address of a stack variable is passed to
free(). Fix it.
Signed-off-by: Pingfan Liu
---
kexec/arch/i386/x86-linux-setup.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kexec/arch/i386/x86-linux-setup.c
E820 reserved ranges is useful in kdump kernel, it has been added in
kexec-tools code.
One reason is PCI mmconf (extended mode) requires reserved region otherwise
it falls back to legacy mode.
When AMD SME kdump support, it needs to map dmi table area as decrypted.
For normal boot, these ranges
E820 reserved ranges is useful in kdump kernel, it has been added in
kexec-tools code.
One reason is PCI mmconf (extended mode) requires reserved region otherwise
it falls back to legacy mode.
Furthermore, when AMD SME kdump support, it needs to map dmi table area as
decrypted. For normal boot,
kdump uses walk_iomem_res_desc() to iterate io resources, then adds matched
desc to e820 table for kdump kernel.
But IORES_DESC_NONE resource type includes several different e820 types,
we need add exact e820 type to kdump kernel e820 table, thus it also needs
an extra checking in
