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: <87wrqwiv1l.fsf@basil.nowhere.org>
Date:	Wed, 08 Sep 2010 08:55:18 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@...el.com>,
	Ingo Molnar <mingo@...e.hu>,
	"tglx\@linutronix.de" <tglx@...utronix.de>,
	"mingo\@redhat.com" <mingo@...hat.com>,
	"x86\@kernel.org" <x86@...nel.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
	"netdev\@vger.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH] [arch-x86] Allow SRAT integrity check to be skipped

"H. Peter Anvin" <hpa@...or.com> writes:
>
> If this is a production BIOS it should have this information.

The point was -- it wasn't a production BIOS and the production
BIOS will be fixed.

If you want you call fill the DMI tables with all bugs in preproduction
BIOS, but I suspect that will fill them up rather quickly. Preproduction
BIOS tend to be buggy (that is why they are pre-production)

Another problem also with adding stuff for early BIOS is that the later
BIOS likely have this fixed and then you have a quirk that runs but is
not needed (unless you add another DMI match for the fixed production
BIOS etc.) While for this case it would be probably harmless, 
this has caused problems in the past with other quirks.

Normally early users are also ok with having to specify an option
as a workaround, they just need something they can specify.

IMHO also it's good coding practice to have a command line option
for every DMI quirk anyways. This makes it easier to let 
users test if they need a particular quirk and helps
with users running older kernels.

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/