linux-kernel - Re: [34-longterm 179/179] x86/PCI: do not tie MSI MS-7253 use

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: <20120515154455.39cfbad2@pyramind.ukuu.org.uk>
Date:	Tue, 15 May 2012 15:44:55 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	<stable@...nel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [34-longterm 179/179] x86/PCI: do not tie MSI MS-7253 use_crs
 quirk to BIOS version

O> MS-7253, for which we already have a quirk, but the short-sighted
> author tied the quirk to a single BIOS version, making it not kick in

It's our usual policy to tie to particular BIOS versions because these
things are often BIOS specific and come and go with updates.

So I think short-sighted is unfair - appropriately conserative is closer.

> on Carlos's machine with BIOS V1.2.  If a later BIOS update makes it
> no longer necessary to look at the _CRS info it will still be
> harmless, so let's stop trying to guess which versions have and don't
> have accurate _CRS tables.

Have you verified there are no BIOSes > v1.6 and that none of them have
release notes or testing showing fixes related to this ? Adding 1.2 is
fine but you are just asking for a regression on 1.7+ or similar.

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