On Sat, 23 Sep 2006, Stas Sergeev wrote:
> Hugh Dickins wrote:
>
> > It's hardly any surprise, is it, that if a distro chooses now
> > to mount something "noexec", a problem is then found with a few
> > things which want otherwise?
> They do not "want otherwise". They do the right thing - use
> shm_open() and then mmap(), but mmap() suddenly fails. The apps
> are not guilty. Neither I think the debian guys are.
Debian wants /dev/shm mounted "noexec" for whatever reason,
these apps want otherwise: to be able to mmap PROT_EXEC on it.
>
> > And it seems unlikely that the answer
> > is then to modify the kernel, to weaken the very protection they're
> > wanting to add?
> I don't think they want to prevent PROT_EXEC mmaps. Almost
> certainly not. Maybe they thought they would only block mere
> execve() calls and the like, I don't know. My point is that
> this change (use of "noexec") should not break the properly
> written apps, but right now it does. Is it stated anywhere
> in the shm_open() manpage or elsewhere that you must not use
> "noexec" on tmpfs or you'll get troubles with mmap?
No, it's not. But this doesn't have much to do with tmpfs,
nor with shm_open. It's just that the kernel is not allowing
mmap PROT_EXEC on a MNT_NOEXEC mount. Which seems reasonable
(though you can argue that mprotect ought to disallow it too).
If that's a problem for something, don't mount "noexec"
(but I'm not the one to recommend a secure configuration).
>
> > The original 2.6.0 patch (later backported into 2.4.25) was
> > <[email protected]>
> > [PATCH] Fix 'noexec' behaviour
> > We should not allow mmap() with PROT_EXEC on mounts marked "noexec",
> > since otherwise there is no way for user-supplied executable loaders
> > (like ld.so and emulator environments) to properly honour the
> > "noexec"ness of the target.
> Thanks for the pointer, but that looks like the user-space
> issue to me. Why ld.so can't figure out the "noexecness" and
> do the right thing itself?
That would be tiresome work.
> Or does it figure out the "noexecness"
> exactly by trying the PROT_EXEC mmap and see if it fails?
Exactly.
Hugh
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
