linux-kernel - Re: pci-disable-decoding-during-sizing-of-bars.patch no longer needed

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: <20080216220025.GI7657@parisc-linux.org>
Date:	Sat, 16 Feb 2008 15:00:26 -0700
From:	Matthew Wilcox <matthew@....cx>
To:	Daniel Drake <dsd@...too.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Greg KH <greg@...ah.com>,
	linux kernel list <linux-kernel@...r.kernel.org>,
	andreas.eckstein@....net,
	Ivan Kokshaysky <ink@...assic.park.msu.ru>
Subject: Re: pci-disable-decoding-during-sizing-of-bars.patch no longer needed

On Sat, Feb 16, 2008 at 09:50:51PM +0000, Daniel Drake wrote:
> Hi,
> 
> The patch titled pci-disable-decoding-during-sizing-of-bars.patch in -mm 
> was previously used as a candidate to fix a boot hang with Intel's Q35 
> chipset: https://bugs.gentoo.org/show_bug.cgi?id=198810
> 
> However, that particular issue is solved by commit a0ca9909609 in Linus 
> tree:
> 	PCI x86: always use conf1 to access config space below 256 bytes
> 
> So unless there are other reasons for keeping 
> pci-disable-decoding-during-sizing-of-bars around, I think we can drop it.

I agree it should be dropped.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
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/