linux-kernel - Re: [patch 0/2] PNP: disable PNP motherboard resources that overlap PCI BARs

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] [day] [month] [year] [list]

Date:	Wed, 12 Mar 2008 00:14:18 +0100
From:	Thomas Renninger <trenn@...e.de>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
	linux-acpi@...r.kernel.org, Len Brown <lenb@...nel.org>,
	Li Shaohua <shaohua.li@...el.com>,
	Matthew Hall <mhall@...omputing.net>,
	Willem Riede <wriede@...de.org>,
	Robert Hancock <hancockr@...w.ca>,
	Karl Bellve <karl.bellve@...ssmed.edu>,
	Avuton Olrich <avuton@...il.com>
Subject: Re: [patch 0/2] PNP: disable PNP motherboard resources that
	overlap PCI BARs


On Tue, 2008-03-11 at 15:24 -0600, Bjorn Helgaas wrote:
> The following two patches fix several problems caused by BIOSes that
> report PNP motherboard device resources that overlap with PCI BARs.
> 
> I think these should go in before 2.6.25 because some of these problems
> showed up in 2.6.24 when we increased PNP_MAX_MEM from 4 to 12, and
> there's no good way to work around them.

I cannot judge about the "cleanness" because of possible changes of
initialization time of pci/pnp or whatever.

I can confirm that ACPI resource declarations (especially (only?) in the
general motherboard devices) are often rather broken.
Therefore I like your general approach compared to the per machine dmi
match quirks. I expect the latter (dmi matching) is rather hopeless.


   Thomas

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