[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <X/wWnGF5ajYk0bf4@kroah.com>
Date: Mon, 11 Jan 2021 10:13:00 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Baoquan He <bhe@...hat.com>
Cc: Alexander Egorenkov <egorenar@...ux.ibm.com>, dyoung@...hat.com,
vgoyal@...hat.com, lijiang@...hat.com, ebiederm@...ssion.com,
akpm@...ux-foundation.org, ktkhai@...tuozzo.com,
keescook@...omium.org, christian.brauner@...ntu.com,
kexec@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/1] kdump: append uts_namespace.name offset to
VMCOREINFO
On Fri, Jan 08, 2021 at 11:32:48AM +0800, Baoquan He wrote:
> 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.
>
> Below tag and CC should have been added into patch when posted.
>
> Fixes: commit 9a56493f6942 ("uts: Use generic ns_common::count")
> Cc: <stable@...r.kernel.org>
>
> Hi Greg,
>
> Do we still have chance to make it added into stable?
Wait, 9a56493f6942 ("uts: Use generic ns_common::count") is in 5.11-rc1,
and this commit fixes that one, so why does anything need to be
backported?
Are you _SURE_ that this commit is needed in 5.10.y?
thanks,
greg k-h
Powered by blists - more mailing lists