All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Baoquan He <bhe@redhat.com>
Cc: lijiang@redhat.com, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Alexander Egorenkov <egorenar@linux.ibm.com>,
	ktkhai@virtuozzo.com, ebiederm@xmission.com,
	akpm@linux-foundation.org, dyoung@redhat.com,
	christian.brauner@ubuntu.com, vgoyal@redhat.com,
	keescook@chromium.org
Subject: Re: [PATCH v3 1/1] kdump: append uts_namespace.name offset to VMCOREINFO
Date: Mon, 11 Jan 2021 10:13:00 +0100	[thread overview]
Message-ID: <X/wWnGF5ajYk0bf4@kroah.com> (raw)
In-Reply-To: <20210108033248.GA4959@MiWiFi-R3L-srv>

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?

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

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Baoquan He <bhe@redhat.com>
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: Mon, 11 Jan 2021 10:13:00 +0100	[thread overview]
Message-ID: <X/wWnGF5ajYk0bf4@kroah.com> (raw)
In-Reply-To: <20210108033248.GA4959@MiWiFi-R3L-srv>

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?

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

  parent reply	other threads:[~2021-01-11  9:14 UTC|newest]

Thread overview: 22+ 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-09-30 10:23 ` Alexander Egorenkov
2020-10-02  2:38 ` lijiang
2020-10-02  2:38   ` lijiang
2020-10-20  2:28 ` Baoquan He
2020-10-20  2:28   ` Baoquan He
2021-01-08  3:32 ` Baoquan He
2021-01-08  3:32   ` Baoquan He
2021-01-08  8:12   ` Greg KH
2021-01-08  8:12     ` Greg KH
2021-01-08  8:48     ` Baoquan He
2021-01-08  8:48       ` Baoquan He
2021-01-08 10:07   ` HAGIO KAZUHITO(萩尾　一仁)
2021-01-08 10:07     ` HAGIO KAZUHITO(萩尾　一仁)
2021-01-08 10:22     ` Baoquan He
2021-01-08 10:22       ` Baoquan He
2021-01-11  9:16       ` gregkh
2021-01-11  9:16         ` gregkh
2021-01-11 10:03         ` Baoquan He
2021-01-11 10:03           ` Baoquan He
2021-01-11  9:13   ` Greg KH [this message]
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=X/wWnGF5ajYk0bf4@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=christian.brauner@ubuntu.com \
    --cc=dyoung@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=egorenar@linux.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.