From: Baoquan He <bhe@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Alexander Egorenkov <egorenar@linux.ibm.com>,
dyoung@redhat.com, vgoyal@redhat.com, lijiang@redhat.com,
ebiederm@xmission.com, akpm@linux-foundation.org,
ktkhai@virtuozzo.com, keescook@chromium.org,
christian.brauner@ubuntu.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/1] kdump: append uts_namespace.name offset to VMCOREINFO
Date: Fri, 8 Jan 2021 16:48:16 +0800 [thread overview]
Message-ID: <20210108084816.GB4959@MiWiFi-R3L-srv> (raw)
In-Reply-To: <X/gT6jQTaFkqqIGt@kroah.com>
On 01/08/21 at 09:12am, Greg KH wrote:
> 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@vger.kernel.org>
> >
> > Hi Greg,
> >
> > Do we still have chance to make it added into stable?
>
> Sure, what is the git commit id of this patch in Linus's tree?
This commit:
ca4a9241cc5e kdump: append uts_namespace.name offset to VMCOREINFO
>
> In the future, please read:
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> for how to do this properly.
Sure, will do as the doc said in the future, thanks a lot for the
pointer.
Thanks
Baoquan
next prev parent reply other threads:[~2021-01-08 8:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 10:23 [PATCH v3 1/1] kdump: append uts_namespace.name offset to VMCOREINFO Alexander Egorenkov
2020-10-02 2:38 ` lijiang
2020-10-20 2:28 ` Baoquan He
2021-01-08 3:32 ` Baoquan He
2021-01-08 8:12 ` Greg KH
2021-01-08 8:48 ` Baoquan He [this message]
2021-01-08 10:07 ` HAGIO KAZUHITO(萩尾 一仁)
2021-01-08 10:22 ` Baoquan He
2021-01-11 9:16 ` gregkh
2021-01-11 10:03 ` Baoquan He
2021-01-11 9:13 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210108084816.GB4959@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=christian.brauner@ubuntu.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=egorenar@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=kexec@lists.infradead.org \
--cc=ktkhai@virtuozzo.com \
--cc=lijiang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox