linux-kernel - Re: [PATCH] Blacklist DMAR on Intel G31/G33 chipsets

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: <1220775618.2985.408.camel@pmac.infradead.org>
Date:	Sun, 07 Sep 2008 09:20:18 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org, andi@...stfloor.org,
	arjan@...radead.org, torvalds@...ux-foundation.org,
	sfr@...b.auug.org.au, Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: [PATCH] Blacklist DMAR on Intel G31/G33 chipsets

On Sat, 2008-09-06 at 17:49 +0200, Ingo Molnar wrote:
> Jesse's call obviously, but the DMI thing local to intel-iommu.c still 
> looks better to me in all regards. I'm no fan of DMI in general - it 
> just doesnt scale - but here a crappy BIOS gets punished with a DMI 
> quirk and that's OK.

The DMI was my first choice too -- I was only trying to do it with PCI
to keep Andi happy.

There is a non-zero possibility that the same BIOS bug gets copied to
other boards, I suppose -- but it's not exactly hard to add another
board to the table if we find that to be the case.

Shall I resubmit the original version to Linus again for 2.6.27, then?

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@...el.com                              Intel Corporation



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