Thread (6 messages) 6 messages, 3 authors, 6d ago

Re: [PATCH RFC] RAS: hwerr_tracking: move recoverable hardware error tracking out of vmcoreinfo

From: Borislav Petkov <bp@alien8.de>
Date: 2026-07-07 18:35:56
Also in: linux-acpi, linux-edac, linux-pci, lkml

On Tue, Jul 07, 2026 at 09:53:34AM -0700, Breno Leitao wrote:
The current vmcoreinfo implementation defaults to enabled, so I wanted to
preserve that behavior to avoid silently removing symbols that existing
tools may depend on. Would you prefer a different default?
You do know Linus' stance on enabling things by default which are not
ubiquitous, right?

Logging hw errors in vmcore is really necessary to be enabled everywhere?
I agree the sysfs exposure duplicates existing infrastructure, points
taken. However, tracking fatal hardware errors provides value at crash
analysis time—it lets us quickly determine whether a fatal hardware
error occurred during the kernel's lifetime, which is useful for
root-cause attribution.
Yes, that's why you put it in vmcore. You can't read sysfs if you encounter
a fatal hw error.
For this, would you like to keep it in vmcore info (as of today), or
move to RAS subsystem?
You mean, would I like to pay attention to more patches than now?

Not really - I can barely manage as it is.

:-)

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help