linux-kernel - Re: [PATCH]PCI:disable resource decode in PCI BAR detection

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: <46EE8F8A.9020104@shaw.ca>
Date:	Mon, 17 Sep 2007 08:30:34 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	Ivan Kokshaysky <ink@...assic.park.msu.ru>
Cc:	Matthew Wilcox <matthew@....cx>, Greg KH <gregkh@...e.de>,
	Shaohua Li <shaohua.li@...el.com>,
	lkml <linux-kernel@...r.kernel.org>,
	linux-pci <linux-pci@...ey.karlin.mff.cuni.cz>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: [PATCH]PCI:disable resource decode in PCI BAR detection

Ivan Kokshaysky wrote:
> On Sun, Sep 16, 2007 at 01:52:59PM -0600, Matthew Wilcox wrote:
>> I don't think it would be that complicated.  We could just delay probing
>> for mmconfig until after the pci bus probes are done.  No changes to
>> other architectures needed.
> 
> Indeed. Seems like it's a way to go.

With another patch pending for 2.6.24, to validate the MMCONFIG aperture 
against the ACPI motherboard resources instead of the E820 table, we 
have to delay switching to MMCONFIG until the ACPI interpreter is 
available (unless no other configuration mechanism is available). It 
might thus be feasible to delay it further.

Nevertheless, I think this is a rather ugly workaround for the 
underlying problem.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@...pamshaw.ca
Home Page: http://www.roberthancock.com/

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