linux-kernel - Re: Really good idea to allow mmap(0, FIXED)?

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: <1160133606.3000.101.camel@laptopd505.fenrus.org>
Date:	Fri, 06 Oct 2006 13:20:05 +0200
From:	Arjan van de Ven <arjan@...radead.org>
To:	Mikael Pettersson <mikpe@...uu.se>
Cc:	David Wagner <daw-usenet@...erner.cs.berkeley.edu>,
	linux-kernel@...r.kernel.org
Subject: Re: Really good idea to allow mmap(0, FIXED)?

On Fri, 2006-10-06 at 12:36 +0200, Mikael Pettersson wrote:
> Arjan van de Ven writes:
>  > >     mmap(0, 4096, PROT_READ|PROT_EXEC|PROT_WRITE,
>  > >         MAP_FIXED|MAP_PRIVATE|MAP_ANONYMOUS, 0, 0);
>  > >     struct s *bar = 0;
>  > 
>  > the question isn't if it's a good idea to allow mmap(0) but to allow
>  > mmap PROT_WRITE | PROT_EXEC !
> 
> It is if you want JITs, code loaders, virtualisation engines, etc
> to continue working.

yeah I know we can't forbid it point blank
(having said that, on architectures where I and D cache aren't coherent
(and there are many, including ia64), most of these are buggy anyway;
the sane ones actually do an mprotect between writing and executing, so
that the kernel can take care of the cache coherency properly)

-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com

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