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]
Date:	Mon, 12 Mar 2012 19:10:47 +0100
From:	Borislav Petkov <bp@...64.org>
To:	"Luck, Tony" <tony.luck@...el.com>
Cc:	Mauro Carvalho Chehab <mchehab@...hat.com>,
	"Mark A. Grondona" <mgrondona@...l.gov>,
	Linux Edac Mailing List <linux-edac@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/6] Add a per-dimm structure

On Mon, Mar 12, 2012 at 05:03:47PM +0000, Luck, Tony wrote:
> > Err, the fact that you have UE counters doesn't have anything to do with
> > the request that you want to panic on an UE. Especially if conservative
> > systems would panic on the first UE anyway without asking software.
> 
> We have some UE events for which even a conservative system might
> think it reasonable to defer the panic (e.g. patrol scrub on a "free" page).

Right, and in that case you don't need an UE counter because it won't go
higher than 1, would it?

What my thought is, is that if the system panics on UE unconditionally
anyway (either by sw or a hw method), then you don't need to enable
panic_on_ue in edac because it does so anyway, and, as a result, you
don't need UE counters at all. So, in that case, you could "state" in
the driver that you don't want to init the UE counters because you're
not going to use them, no?

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ