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] [day] [month] [year] [list]
Message-ID: <CA+=Fv5Q6pmCZOm1CE9uoW8YNQtbg8o67ACDxGGjLUy+-KtfVXw@mail.gmail.com>
Date: Thu, 24 Apr 2025 22:38:04 +0200
From: Magnus Lindholm <linmag7@...il.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: linux-kernel@...r.kernel.org, linux-alpha@...r.kernel.org, 
	Richard Henderson <richard.henderson@...aro.org>, Matt Turner <mattst88@...il.com>, 
	"Paul E. McKenney" <paulmck@...nel.org>, 
	John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>, macro@...hat.com, 
	Michael Cree <mcree@...on.net.nz>, Ivan Kokshaysky <ink@...een.parts>
Subject: Re: [PATCH v2] alpha: machine check handler for tsunami

> Should this perhaps be part of drivers/edac/ ?
>
>      ARnd

In that case we should, for consistency, also move machine check code
for other alpha families as well. Some of the machine check errors are for sure
"edac" but the memory/ecc error is just a subset of all the possible machine
check exceptions. Stuff like power supply errors, temperatures and such may not
belong in edac? I guess it would be possible to handle machine check exceptions
caused by memory errors through an edac driver and the rest of the machine
check exceptions through the "regular" alpha machine check handlers.

/Magnus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ