From: Baoquan He <bhe@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Breno Leitao <leitao@debian.org>
Cc: vgoyal@redhat.com, dyoung@redhat.com, xueshuai@linux.alibaba.com,
tony.luck@intel.com, linux-kernel@vger.kernel.org,
osandov@osandov.com, kernel-team@meta.com
Subject: Re: [PATCH v2] vmcoreinfo: make hwerr_data visible for debugging
Date: Sat, 24 Jan 2026 09:58:59 +0800 [thread overview]
Message-ID: <aXQnY4izGQUgvFvk@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20260123164950.6988b5fe7e11d5986e399752@linux-foundation.org>
On 01/23/26 at 04:49pm, Andrew Morton wrote:
> On Fri, 23 Jan 2026 01:24:17 -0800 Breno Leitao <leitao@debian.org> wrote:
>
> > Hello Baoquan,
> >
> > On Fri, Jan 23, 2026 at 08:19:40AM +0800, Baoquan He wrote:
> > > On 01/22/26 at 02:39am, Breno Leitao wrote:
> > > > If the kernel is compiled with LTO, hwerr_data symbol might be lost, and
> > > > vmcoreinfo doesn't have it dumped. This is currently seen in some
> > > > production kernels with LTO enabled.
> > > >
> > > > Remove the static qualifier from hwerr_data so that the information is
> > > > still preserved when the kernel is built with LTO. Making hwerr_data
> > > > a global symbol ensures its debug info survives the LTO link process and
> > > > appears in kallsyms. Also document it, so, it doesn't get removed in the
> > > > future as suggested by akpm.
> > > >
> > > > Signed-off-by: Breno Leitao <leitao@debian.org>
> > > > ---
> > > > Changes in v2:
> > > > - Add a comment to explain why the array is global (akpm)
> > > > - Link to v1: https://patch.msgid.link/20260121-fix_vmcoreinfo-v1-1-39e96fab670e@debian.org
> > > > ---
> > > > kernel/vmcore_info.c | 6 +++++-
> > > > 1 file changed, 5 insertions(+), 1 deletion(-)
> > >
> > > LGTM,
> > >
> > > Acked-by: Baoquan He <bhe@redhat.com>
> > >
> > > BTW, is it worth a 'Fixes' tag?
> >
> > I am not sure, but, if we prefer to, this is the correct tag:
> >
> > Fixes: 3fa805c37dd4d ("vmcoreinfo: track and log recoverable hardware errors")
>
> 3fa805c37dd4d was added in 6.19-rc1, so this patch is a fixup against
> this rc series. So yes, it should go into 6.19-rcX also.
Ah, then no need. thanks.
prev parent reply other threads:[~2026-01-24 1:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 10:39 [PATCH v2] vmcoreinfo: make hwerr_data visible for debugging Breno Leitao
2026-01-23 0:19 ` Baoquan He
2026-01-23 9:24 ` Breno Leitao
2026-01-24 0:49 ` Andrew Morton
2026-01-24 1:58 ` Baoquan He [this message]
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=aXQnY4izGQUgvFvk@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dyoung@redhat.com \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osandov@osandov.com \
--cc=tony.luck@intel.com \
--cc=vgoyal@redhat.com \
--cc=xueshuai@linux.alibaba.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.