| 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: <8bd0f97a0703261321h356a849am1ab617f0e732fa67@mail.gmail.com> Date: Mon, 26 Mar 2007 16:21:51 -0400 From: "Mike Frysinger" <vapier.adi@...il.com> To: "David Howells" <dhowells@...hat.com> Cc: "Pekka J Enberg" <penberg@...helsinki.fi>, "Andrew Morton" <akpm@...ux-foundation.org>, bryan.wu@...log.com, linux-kernel@...r.kernel.org, "Hugh Dickins" <hugh@...itas.com>, "Alan Cox" <alan@...rguk.ukuu.org.uk> Subject: Re: [PATCH -mm] Revoke core code: fix nommu arch compiling error bug On 3/26/07, David Howells <dhowells@...hat.com> wrote: > [*] The FRV, for example, does have some limited protection capability - but > it is really limited and not really useful in this case. how so ? the Blackfin processor lacks a MMU but it does have a MPU (memory protection unit) which allows granularity down to 1k page sizes ... so for future releases, we plan on integrating optional support for this so that you could have processes protected from each other and the kernel protected from all the processes ... so in our case, we might actually be able to support revoking of maps because we would have that region of memory ear marked as unaccessible ... note that the Blackfin processor manuals confusingly call this aspect of the chip an "MMU" ... dont be fooled ! -mike - 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