| 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
| ||
|
Message-ID: <47A2086F.2040501@zytor.com> Date: Thu, 31 Jan 2008 09:42:07 -0800 From: "H. Peter Anvin" <hpa@...or.com> To: Arjan van de Ven <arjan@...radead.org> CC: Jan Engelhardt <jengelh@...putergmbh.de>, linux-kernel@...r.kernel.org, davej@...hat.com, mingo@...e.hu, tglx@...x.de Subject: Re: [PATCH] x86: introduce /dev/mem restrictions with a config option Arjan van de Ven wrote: > On Thu, 31 Jan 2008 17:53:04 +0100 (CET) > Jan Engelhardt <jengelh@...putergmbh.de> wrote: > >> On Jan 30 2008 12:48, Arjan van de Ven wrote: >>> Subject: [PATCH] x86: introduce /dev/mem restrictions with a config >>> option >>> >>> This patch introduces a restriction on /dev/mem: Only non-memory can >>> be read or written unless the newly introduced config option is set. >> Would not it be nicer to add a /dev/pcimem that implements the given >> restrictive semantics? >> >> Maybe it's just wishful thinking, but I am dreaming of an >> unprivileged X, and /dev/pcimem (owned by an 'x11' user or so) would >> be a step in that direction. > > /dev/pcimem is wrong; X can use the exact bar in sysfs already. > This is more for compatibility with legacy X > Legacy X, and non-BAR X memory (originally ISA, of course; now probably more often "stolen system memory"). -hpa -- 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/
Powered by blists - more mailing lists