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: <476F9DF6.60100@garzik.org>
Date:	Mon, 24 Dec 2007 06:54:30 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Arjan van de Ven <arjan@...radead.org>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, gregkh@...e.de,
	linux-pci@...ey.karlin.mff.cuni.cz,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Subject: Re: [patch] Make MMCONFIG space (extended PCI config space) a driver
 opt-in issue

Arjan van de Ven wrote:
> I can see the point of having a sysfs attribute to enable MMCONF from userspace, so
> that userland diagnostics tools can turn it on if they really really want to.
> (I'd make that printk a nice warning "application XYZ is enabling extended config space for devize ABC" so
> that if the box then crashes and burns, people know who/why and where to direct their emails ;-)
> 
> We did something similar for "enable", it's maybe 10 lines of code or so.
> 
> I would assume lspci and friends would then only turn that on at explicit admin request

Absolutely...  I'm not asking to default it on, just asking for it to be 
possible :)

	Jeff


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