Re: [PATCHv7] x86/kdump: bugfix, make the behavior of crashkernel=X consistent with kaslr

On Fri, Feb 01, 2019 at 12:47:40AM +0100, Borislav Petkov wrote: > On Thu, Jan 31, 2019 at 03:27:32PM -0700, Jerry Hoemann wrote: > > So even if a system administrator is diligent and tests > > that a chosen kdump configuration works, that configuration > > might not work on some random reboot 7 mo

Re: [PATCH] integrity, KEYS: Fix build break with set_platform_trusted_keys

On Sun, 2019-02-03 at 23:59 +0800, Kairui Song wrote: > Commit 15ebb2eb0705 ("integrity, KEYS: add a reference to platform > keyring") introduced a function set_platform_trusted_keys > and calls the function in __integrity_init_keyring. > > It only checks if CONFIG_INTEGRITY_PLATFORM_KEYRING is en

[PATCH] x86, kexec_file_load: fill in acpi_rsdp_addr boot param unconditionally

When efi=noruntime or efi=oldmap is used, EFI services won't be available in the second kernel, therefore the second kernel will not be able to get the ACPI RSDP address from firmware by calling EFI services so it won't boot. Previously we are expecting the user to set the acpi_rsdp= on kernel comm

RE: [PATCH v3] Remove the memory encryption mask to obtain the true physical address

> [PATCH v3] Remove the memory encryption mask to obtain the true physical > address I forgot to comment on the subject and the commit log.. I'll change this to x86_64: Add support for AMD Secure Memory Encryption On 1/29/2019 9:48 PM, Lianbo Jiang wrote: > For AMD machine with SME feature, i

Re: [PATCH] arm64, vmcoreinfo : Append 'MAX_USER_VA_BITS' and 'MAX_PHYSMEM_BITS' to vmcoreinfo

Hi Bhupesh, On 04/02/2019 14:35, Bhupesh Sharma wrote: > On 01/31/2019 03:09 AM, Bhupesh Sharma wrote: >> On 01/30/2019 08:51 PM, James Morse wrote: >>> On 01/30/2019 12:23 PM, Bhupesh Sharma wrote: With ARMv8.2-LVA and LPA architecture extensions, arm64 hardware which supports these ext

Re: [PATCH 1/2] arm64: Expose address bits (physical/virtual) via cpuinfo

Hi Bhupesh, On 30/01/2019 19:48, Bhupesh Sharma wrote: > On 01/29/2019 03:39 PM, Suzuki K Poulose wrote: >> On 28/01/2019 20:57, Bhupesh Sharma wrote: >>> With ARMv8.2-LVA and LPA architecture extensions, arm64 hardware which >>> supports these extensions can support upto 52-bit virtual and 52-bit

RE: [PATCH] arm64, vmcoreinfo : Append 'MAX_USER_VA_BITS' and 'MAX_PHYSMEM_BITS' to vmcoreinfo

On 1/30/2019 8:48 PM, Dave Young wrote: > + more people > On 01/30/19 at 05:53pm, Bhupesh Sharma wrote: > > With ARMv8.2-LVA and LPA architecture extensions, arm64 hardware which > > supports these extensions can support upto 52-bit virtual and 52-bit > > physical addresses respectively. > > > > Si

Re: [PATCH] arm64, vmcoreinfo : Append 'MAX_USER_VA_BITS' and 'MAX_PHYSMEM_BITS' to vmcoreinfo

On 04/02/2019 14:35, Bhupesh Sharma wrote: [...] Also hardcoding the PTE calculation to use the high address bit mask always will break the backward compatibility with older kernels (which don't support 52-bit address space extensions). No it won't. There's no difference between an old kernel,

Re: [PATCH] arm64, vmcoreinfo : Append 'MAX_USER_VA_BITS' and 'MAX_PHYSMEM_BITS' to vmcoreinfo

Hi James, All, On 01/31/2019 03:09 AM, Bhupesh Sharma wrote: Hi James, Thanks for review. Please see my comments inline. On 01/30/2019 08:51 PM, James Morse wrote: Hi Bhupesh, On 01/30/2019 12:23 PM, Bhupesh Sharma wrote: With ARMv8.2-LVA and LPA architecture extensions, arm64 hardware whi

Re: [PATCH 3/3] selftests/ima: kexec_file_load syscall test

On Sun, 2019-02-03 at 23:02 +0100, Petr Vorel wrote: > Hi Mimi, > > > The kernel can be configured to verify PE signed kernel images, IMA > > kernel image signatures, both types of signatures, or none. This test > > verifies only properly signed kernel images are loaded into memory, > > based on