[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210108102224.GC4959@MiWiFi-R3L-srv>
Date: Fri, 8 Jan 2021 18:22:24 +0800
From: Baoquan He <bhe@...hat.com>
To: HAGIO KAZUHITO(萩尾 一仁)
<k-hagio-ab@....com>
Cc: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"lijiang@...hat.com" <lijiang@...hat.com>,
"kexec@...ts.infradead.org" <kexec@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"ktkhai@...tuozzo.com" <ktkhai@...tuozzo.com>,
"ebiederm@...ssion.com" <ebiederm@...ssion.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"dyoung@...hat.com" <dyoung@...hat.com>,
"christian.brauner@...ntu.com" <christian.brauner@...ntu.com>,
"vgoyal@...hat.com" <vgoyal@...hat.com>,
"keescook@...omium.org" <keescook@...omium.org>,
Alexander Egorenkov <egorenar@...ux.ibm.com>
Subject: Re: [PATCH v3 1/1] kdump: append uts_namespace.name offset to
VMCOREINFO
On 01/08/21 at 10:07am, HAGIO KAZUHITO(萩尾 一仁) wrote:
> Hi Baoquan,
>
> -----Original Message-----
> > On 09/30/20 at 12:23pm, Alexander Egorenkov wrote:
> > > The offset of the field 'init_uts_ns.name' has changed
> > > since commit 9a56493f6942 ("uts: Use generic ns_common::count").
> >
> > This patch is merged into 5.11-rc1, but we met the makedumpfile failure
> > of kdump test case in 5.10.0 kernel. Should affect 5.9 too since
> > commit 9a56493f6942 is merged into 5.9-rc2.
>
> Hmm, commit 9a56493f6942 should have been merged into 5.11-rc1
> together with commit ca4a9241cc5e.
Checked on master branch of mainline kernel, commit 9a56493f6942 is in
5.9-rc1. commit ca4a9241cc5e is merged into 5.11-rc1.
commit 9a56493f6942c0e2df1579986128721da96e00d8
Author: Kirill Tkhai <ktkhai@...tuozzo.com>
Date: Mon Aug 3 13:16:21 2020 +0300
uts: Use generic ns_common::count
commit ca4a9241cc5e718de86a34afd41972869546a5e3
Author: Alexander Egorenkov <egorenar@...ux.ibm.com>
Date: Tue Dec 15 20:45:31 2020 -0800
kdump: append uts_namespace.name offset to VMCOREINFO
>
> Does your makedumpfile have the following patch?
> https://github.com/makedumpfile/makedumpfile/commit/54aec3878b3f91341e6bc735eda158cca5c54ec9
We met this issue on 5.10 kernel, the latest makedumpfile 1.6.8+ fixs
it. Makedumpfile 1.6.8+ includes the commit 54aec3878b3f. Not sure if I
got the kernel commit right in their corresponding release.
Thanks
Baoquan
Powered by blists - more mailing lists