From: "dyoung@redhat.com" <dyoung@redhat.com>
To: "HAGIO KAZUHITO(萩尾 一仁)" <k-hagio-ab@nec.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
bhe@redhat.com, Alexander Egorenkov <egorenar@linux.ibm.com>
Subject: Re: [PATCH 1/1] kdump: append uts_namespace.name offset to VMCOREINFO
Date: Wed, 23 Sep 2020 14:00:12 +0800 [thread overview]
Message-ID: <20200923060012.GA5347@dhcp-128-65.nay.redhat.com> (raw)
In-Reply-To: <OSBPR01MB1991B0822ACE45077105DD46DD380@OSBPR01MB1991.jpnprd01.prod.outlook.com>
Hi Kazu,
On 09/23/20 at 04:37am, HAGIO KAZUHITO(萩尾 一仁) wrote:
> Hi Dave,
>
> sorry to bother you. We need this kernel patch to fix a makedumpfile issue
> with the current linux-next. Should we send this to the addresses below, right?
> I'm not sure whether they are enough.
It is good, but I suggest also cc Eric:
"Eric W. Biederman" <ebiederm@xmission.com>
BTW, the -next commit log should mention which branch the commit stays, and it
would be better to add the original discussion link eg. the patch link on
lore.kernel.org
>
> Alex,
>
> Thanks for the patch. Since this patch is for kernel, it needs to be sent
> to kernel maintainers and mailing lists, and I think you can get their
> addresses with scripts/get_maintainer.pl in the kernel tree.
>
> $ scripts/get_maintainer.pl /tmp/a.patch
> Dave Young <dyoung@redhat.com> (maintainer:KDUMP)
> Baoquan He <bhe@redhat.com> (maintainer:KDUMP)
> Vivek Goyal <vgoyal@redhat.com> (reviewer:KDUMP)
> kexec@lists.infradead.org (open list:KDUMP)
> linux-kernel@vger.kernel.org (open list)
>
> Thanks,
> Kazu
>
> -----Original Message-----
> > The offset of the field 'init_uts_ns.name' has changed
> > since commit 9a56493f6942c0e2df1579986128721da96e00d8.
> > Make the offset of the field 'uts_namespace.name' available
> > in VMCOREINFO because tools like 'crash-utility' and
> > 'makedumpfile' must be able to read it from crash dumps.
> >
> > Signed-off-by: Alexander Egorenkov <egorenar@linux.ibm.com>
> > ---
> > kernel/crash_core.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/kernel/crash_core.c b/kernel/crash_core.c
> > index 106e4500fd53..173fdc261882 100644
> > --- a/kernel/crash_core.c
> > +++ b/kernel/crash_core.c
> > @@ -447,6 +447,7 @@ static int __init crash_save_vmcoreinfo_init(void)
> > VMCOREINFO_PAGESIZE(PAGE_SIZE);
> >
> > VMCOREINFO_SYMBOL(init_uts_ns);
> > + VMCOREINFO_OFFSET(uts_namespace, name);
> > VMCOREINFO_SYMBOL(node_online_map);
> > #ifdef CONFIG_MMU
> > VMCOREINFO_SYMBOL_ARRAY(swapper_pg_dir);
> > --
> > 2.26.2
> >
> >
> > _______________________________________________
> > kexec mailing list
> > kexec@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/kexec
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
>
Thanks
Dave
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2020-09-23 6:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 8:04 [PATCH 1/1] kdump: append uts_namespace.name offset to VMCOREINFO Alexander Egorenkov
2020-09-23 4:37 ` HAGIO KAZUHITO(萩尾 一仁)
2020-09-23 6:00 ` dyoung [this message]
2020-09-23 6:04 ` dyoung
2020-09-24 1:32 ` HAGIO KAZUHITO(萩尾 一仁)
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=20200923060012.GA5347@dhcp-128-65.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=bhe@redhat.com \
--cc=egorenar@linux.ibm.com \
--cc=k-hagio-ab@nec.com \
--cc=kexec@lists.infradead.org \
/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