linux-kernel - Re: [PATCH] corruption checker: print the DMI board name

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]

Date:	Thu, 30 Oct 2008 06:28:30 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Pavel Machek <pavel@...e.cz>
Cc:	mingo@...e.hu, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] corruption checker: print the DMI board name

On Thu, 30 Oct 2008 12:06:53 +0100
Pavel Machek <pavel@...e.cz> wrote:

> > 
> > >From 4f829eef5a31b68a0cbaf83a75ac8b0a1ed05afb Mon Sep 17 00:00:00
> > >2001
> > From: Arjan van de Ven <arjan@...ux.intel.com>
> > Date: Wed, 29 Oct 2008 09:13:23 -0700
> > Subject: [PATCH] corruption checker: print the DMI board name
> > 
> > when the memory corruptor checker hits (as it has done now based on
> > kerneloops.org data), it would be extremely useful to know the DMI
> > board name so we can add a blacklist for such a machine... without
> > having to ask the user for lots of extra info.
> 
> I'm not sure if blacklisting whole brand for one case of bit
> corruption is fair -- perhaps the memory was overheating?

this is where kerneloops.org comes in; we can separate the "happens a
lot" from "happens on blue moons"

> 
>   
> > Signed-off-by: Arjan van de Ven <arjan@...ux.intel.com>
> 
> But ACK -- we certainly want to see the data.
--
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/