linux-kernel - Re: [PATCH RESEND v5] vmcoreinfo: Track and log recoverable hardware errors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20251125093211.081d4ba0e18f1f9a85a0de5f@linux-foundation.org>
Date: Tue, 25 Nov 2025 09:32:11 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Breno Leitao <leitao@...ian.org>, tony.luck@...el.com,
 linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
 acpica-devel@...ts.linux.dev, osandov@...ndov.com,
 xueshuai@...ux.alibaba.com, konrad.wilk@...cle.com,
 linux-edac@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
 linux-pci@...r.kernel.org, kernel-team@...a.com, "Rafael J. Wysocki"
 <rafael@...nel.org>, Len Brown <lenb@...nel.org>, James Morse
 <james.morse@....com>, Robert Moore <robert.moore@...el.com>, Thomas
 Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, Dave Hansen
 <dave.hansen@...ux.intel.com>, x86@...nel.org, "H. Peter Anvin"
 <hpa@...or.com>, Hanjun Guo <guohanjun@...wei.com>, Mauro Carvalho Chehab
 <mchehab@...nel.org>, Mahesh J Salgaonkar <mahesh@...ux.ibm.com>, Oliver
 O'Halloran <oohall@...il.com>, Bjorn Helgaas <bhelgaas@...gle.com>
Subject: Re: [PATCH RESEND v5] vmcoreinfo: Track and log recoverable
 hardware errors

On Tue, 18 Nov 2025 15:10:02 +0100 Borislav Petkov <bp@...en8.de> wrote:

> On Tue, Nov 18, 2025 at 05:01:47AM -0800, Breno Leitao wrote:
> > Do you know what is the right tree for this patch?
> > 
> > I am wondering if it should go through Kdump, x86 or RAS/MCE tree?
> 
> I can take it if akpm wants me to...
> 

I don't feel I'll add much value here so please take it via the
appropriate tree.

I'll toss it in mm.git for linux-next exposure and shall drop it again
when it appears in -next via another route.

It's a shame it took us two weeks to get onto this - it's a bit late
for the upcoming merge window.