linux-kernel - Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue

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: <20071222121503.3502382a@laptopd505.fenrus.org>
Date:	Sat, 22 Dec 2007 12:15:03 -0800
From:	Arjan van de Ven <arjan@...radead.org>
To:	Martin Mares <mj@....cz>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Jeff Garzik <jeff@...zik.org>, linux-kernel@...r.kernel.org,
	gregkh@...e.de, linux-pci@...ey.karlin.mff.cuni.cz
Subject: Re: [patch] Make MMCONFIG space (extended PCI config space) a
 driver opt-in issue

On Sat, 22 Dec 2007 20:30:58 +0100
Martin Mares <mj@....cz> wrote:

> Hello!
> 
> > Just make it so. The name is fine, the concept is unavoidable. The
> > people who complain are whiners that haven't ever had to deal with
> > the fact that there are broken machines around. 
> 
> I complain as well as the maintainer of the pciutils. Breaking all
> userspace accesses to extended configuration space just because there
> is a couple of chipsets

it's not "just a couple of chipsets", it's actually
* a whole lot of bioses
* at least one whole CPU generation
* ..
* ..

Do you really want to code all of that into your userspace access code as well?
--
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/