On Thu, 26 Apr 2018 18:35:10 +0530 Mahesh Jagannath Salgaonkar <mah...@linux.vnet.ibm.com> wrote:
> On 04/26/2018 06:28 PM, Nicholas Piggin wrote: > > On Thu, 26 Apr 2018 17:12:03 +0530 > > Mahesh J Salgaonkar <mah...@linux.vnet.ibm.com> wrote: > > > >> From: Mahesh Salgaonkar <mah...@linux.vnet.ibm.com> > >> > >> otherwise the fadump registration in new kexec-ed kernel complains that > >> fadump is already registered. This makes new kernel to continue using > >> fadump registered by previous kernel which may lead to invalid vmcore > >> generation. Hence this patch fixes this issue by un-registering fadump > >> in fadump_cleanup() which is called during kexec path so that new kernel > >> can register fadump with new valid values. > > > > I assume this series is for 4.17, but it might be good to get this one > > into the 4.16 fixes branch? Should it go to stable kernels? > > You are right. Should I send it out as separate patch ? Yes I think so. Thanks, Nick
