linux-kernel - Re: [PATCH 2/3] x86, RAS: Add a decoded msg buffer

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: <20120302095548.GB7907@aftab>
Date:	Fri, 2 Mar 2012 10:55:49 +0100
From:	Borislav Petkov <bp@...64.org>
To:	"Luck, Tony" <tony.luck@...el.com>
Cc:	Ingo Molnar <mingo@...e.hu>,
	EDAC devel <linux-edac@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/3] x86, RAS: Add a decoded msg buffer

On Wed, Feb 29, 2012 at 11:11:46AM +0100, Borislav Petkov wrote:
> > Is there some upper bound for how long this string can get? Why not
> > just allocate a generous amount at boot time?
> 
> Yep, this sounds like the easiest thing to do, let me play with MCE
> injection a bit.

So I left it inject all kinds of errors overnight and the buffer got
enlarged to 400 bytes:

[ 1115.162484] Buffer enlarged to 250
[ 1115.166059] Buffer enlarged to 300
[ 1115.169604] Buffer enlarged to 350
[ 3855.129854] Buffer enlarged to 400

So I'm guessing something like 500 bytes would be a safe bet in the
current situation.

Now whether 500 bytes is a lot or not, dunno, we'll see how it plays
out in testing. Also, the question is what would happen if we need to
enlarge it later for some more info, hm. Maybe I should go over the
decoded strings and try slimming them up a bit...

-- 
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/