On 2017-07-29 18:38, Timo Paulssen wrote:
However, an executable heap is still necessary even though an
executable stack is not needed when MoarVM built to use libffi 3.1 or
later:
This is most likely due to the jit, which allocates a frame, generates
machine code into it, then jumps into it. Can you check if the
environment variable MVM_JIT_DISABLE makes it work even with deny_execmem?
Yes, that makes it work even with deny_execmem:
[markmont@f26test rakudo-star-2017.07]$ getsebool deny_execmem
deny_execmem --> on
[markmont@f26test rakudo-star-2017.07]$ env MVM_JIT_DISABLE=1 perl6 -e
"say 'hello, world';"
hello, world
[markmont@f26test rakudo-star-2017.07]$
Maybe we can react to not being allowed to set the page executable and
just turn off the jit "forever" at run time.
thanks
- Timo
Thanks for the insight! I'm not sure if turning off JIT is a good
thing, but it's great to know what is happening and why.
--
Mark Montague
m...@catseye.org
