https://bugs.exim.org/show_bug.cgi?id=2445
Zoltan Herczeg <hzmester@???> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hzmester@???
--- Comment #1 from Zoltan Herczeg <hzmester@???> ---
The sljitProtExecAllocator is still an experimental code. It cannot support
fork, and you probably found another Linux weakness. Although ftruncate(fd,
size) is successful, Linux still terminates the process when you fill the
temporary file with data.
https://linux.die.net/man/2/ftruncate
It says:
If the file previously was larger than this size, the extra data is lost. If
the file previously was shorter, it is extended, and the extended part reads as
null bytes ('\0').
I think it should fail if not enough disk space, but it seems it assigns the
same zero page to the file several times and simply crash when copy-on-write
fails. Do you have any idea how to fix this? Creating a temporary signal
handler, writing data, capturing segfault seems an awkward way to handle this.
About why sljitProtExecAllocator is experimental: on hardened systems, you
probably don't want to use jit compilation anyway, so spending too much effort
on this probably gain little benefit.
--
You are receiving this mail because:
You are on the CC list for the bug.
