Re: [PATCH] x86/kdump: Fix 'kmem -s' reported an invalid freepointer when SME was active

On 09/27/19 at 09:32pm, Eric W. Biederman wrote: > Baoquan He writes: > > > On 09/27/19 at 03:49pm, Eric W. Biederman wrote: > >> Dave Young writes: > >> >> In order to avoid such problem, lets occupy the first 640k region when > >> >> SME is active, which will ensure that the allocated memory d

Re: [PATCH] x86/kdump: Fix 'kmem -s' reported an invalid freepointer when SME was active

Baoquan He writes: > On 09/27/19 at 03:49pm, Eric W. Biederman wrote: >> Dave Young writes: >> >> In order to avoid such problem, lets occupy the first 640k region when >> >> SME is active, which will ensure that the allocated memory does not fall >> >> into the first 640k area. So, no need to w

Re: [PATCH] x86/kdump: Fix 'kmem -s' reported an invalid freepointer when SME was active

On 09/27/19 at 03:49pm, Eric W. Biederman wrote: > Dave Young writes: > >> In order to avoid such problem, lets occupy the first 640k region when > >> SME is active, which will ensure that the allocated memory does not fall > >> into the first 640k area. So, no need to worry about whether kernel c

Re: [PATCH] x86/kdump: Fix 'kmem -s' reported an invalid freepointer when SME was active

On 09/27/19 at 03:49pm, Eric W. Biederman wrote: > >> In order to avoid such problem, lets occupy the first 640k region when > >> SME is active, which will ensure that the allocated memory does not fall > >> into the first 640k area. So, no need to worry about whether kernel can > >> correctly copy

Re: [PATCH] x86/kdump: Fix 'kmem -s' reported an invalid freepointer when SME was active

Dave Young writes: > Hi Lianbo, > > For kexec/kdump patches, please remember to cc kexec list next time. > Also it is definitely kdump specific issue, I added Vivek and Eric in > cc. > > On 09/20/19 at 11:53am, Lianbo Jiang wrote: >> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=204793 >

RE: makedumpfile: Fix divide by zero in print_report()

> -Original Message- > On Thu, Sep 26, 2019 at 06:41:48PM +, Kazuhito Hagio wrote: > > > > -Original Message- > > > If info->max_mapnr and pfn_memhole are equal, we divide by zero when > > > trying determine the 'shrinking' value. > > > > > > On the system I saw this error

Re: [PATCH v3 2/2] x86/kdump: Reserve extra memory when SME or SEV is active

On Fri, Sep 27, 2019 at 1:42 PM Dave Young wrote: > > On 09/25/19 at 06:36pm, Kairui Song wrote: > > On Wed, Sep 11, 2019 at 1:56 PM Ingo Molnar wrote: > > > * Kairui Song wrote: > > > > > > > Since commit c7753208a94c ("x86, swiotlb: Add memory encryption > > > > support"), > > > > SWIOTLB wil