linux-kernel - Re: [PATCH] [arch-x86] Allow SRAT integrity check to be skipped

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: <20100903063934.GA25863@elte.hu>
Date:	Fri, 3 Sep 2010 08:39:34 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@...el.com>,
	tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
	x86@...nel.org, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: [PATCH] [arch-x86] Allow SRAT integrity check to be skipped

* Andi Kleen <andi@...stfloor.org> wrote:

> > This isnt a particularly useful solution to users of said systems - 
> > they have to figure out that this option exists, and then they have 
> > to enter this option on the boot line.
> 
> This usually only happens in early preproduction systems. So far the 
> BIOS always got fixed before they shipped to users.

'Usually' != 'always'. Read the changelog:

  ' There are BIOSes in production that have these failures, so this will 
    allow people in the field to work around these BIOS issues. '

Peter, which system in production that has this problem? That one needs 
a DMI match.

Preproduction systems can certainly be hacked around with the boot 
option and are not worth the DMI match. (preproduction systems also tend 
to have have very unspecific DMI strings in most cases - things like 
'1234567890' or 'to be filled by OEM')

In important cases a PCI ID match can be done for serious bugs in 
widespread preproduction systems - we have a handful of examples in-tree 
for such workarounds - but i doubt this is such a case - we use it for 
crasher bugs, not for 'boots up slow' cases.

Nevertheless, production systems need a DMI match.

Thanks,

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