Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 14 Feb 2017 20:21:35 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-fs@FreeBSD.org
Subject:   [Bug 217062] for file systems mounted with -o noexec, exec=off property does not work for mmap
Message-ID:  <bug-217062-3630-zPC2AXynVo@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-217062-3630@https.bugs.freebsd.org/bugzilla/>
References:  <bug-217062-3630@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217062

--- Comment #6 from shamaz.mazum@gmail.com ---
(In reply to Konstantin Belousov from comment #4)

Thanks for the fix. This discrepancy between mmap and mprotect made me think
that there was a bug there. If you are interested, I noticed that, as I said
before, trying to launch SBCL (Steel Bank Common Lisp) with a core image st=
ored
in my home no-exec file system. It failed to start because it maps core ima=
ge
in memory and then calls mprotect for those mappings. But when I opened a
shared library using foreign functions interface, it worked perfectly (I
believe dynamic linker uses mmap).

> If you determined, there is nothing which could prevent you from mapping =
anonymous memory, copying data from the file into it, and then executing.

Yes, you are right. Too bad for my paranoia ;)

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217062-3630-zPC2AXynVo>