| 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: <20081006102739.16d1a434@lxorguk.ukuu.org.uk> Date: Mon, 6 Oct 2008 10:27:39 +0100 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Arjan van de Ven <arjan@...radead.org> Cc: linux-kernel@...r.kernel.org Subject: Re: RFC: banning device driver reserved resources from /dev/mem > This patch adds, to the existing config option to restrict /dev/mem, the > reserved regions to the "banned from /dev/mem use" list, so now > both kernel memory and device-exclusive MMIO regions are banned. This breaks a whole class of diagnostic and debug tools which quite intentionally dump the MMIO register space of devices that are live. Plus it doesn't actually work - if I have /dev/mem open and mmapped you don't pull the pages from under me.... The problem with the way this is going is the more you take from /dev/mem the sooner someone is forced to add /dev/mem-proper which undoes it all again so they can get work done. It's certainly a useful debug aid to know about such things but I don't believe it's something you should ban. Alan -- 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