linux-kernel - Re: [PATCH -mm] 0/2: PCI MMCONFIG-related updates

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: <200705300821.11555.jbarnes@virtuousgeek.org>
Date:	Wed, 30 May 2007 08:21:11 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Robert Hancock <hancockr@...w.ca>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH -mm] 0/2: PCI MMCONFIG-related updates

On Tuesday, May 29, 2007 9:01:22 Robert Hancock wrote:
> These two patches implement some changes in behavior related to PCI
> MMCONFIG configuration space access. One changes the way in which we
> validate the MCFG table provided by the BIOS by checking it against
> ACPI motherboard resources instead of the E820 table. The BIOS is not
> required to reserve this area in the E820 table, so checking that
> results in MMCONFIG being unnecessarily disabled on some machines.
>
> Some Intel chipsets where MMCONFIG was being disabled previously
> (but won't be with the first patch) had problems, not due to the
> MCFG table being broken, but because the access was hosed by the way
> in which we do PCI BAR sizing. The second patch fixes this problem.
>
> This is requested for inclusion in the -mm tree for testing.

Robert, should we also pull in the 915 and 965 chipset specific register 
poking code?  It might be a good sanity check against ACPI (i.e. if ACPI and 
the actual register window disagree, we can assume the BIOS is broken and 
MCFG is not safe to use).  If so, I'll update and repost them against your 
patchset.

Thanks,
Jesse
-
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/