:Another interim solution would be to `fix' GNU grep so it doesn't
:attempt to read() into mmap()'d space. (Having not looked at the
:code, I don't know how difficult this would be).
:
:As for the general problem, is it sensible to allow a read-only file to
:be mmap'd R/W (with or without MAP_PRIVATE) and then written into? It
:would be fairly easy to make mmap() return EACCES if the fd was not
:open for writing (or map the memory R/O and SEGV on a write).
:
:I would personally prefer to see a process die with an mmap failure
:(or SIGSEGV), rather than cause a deadlock - ie even if we do want/
:...
We really need to fix the kernel, I think. This sort of deadlock
situation has been a problem for too long and it is only going to
get worse as more programs use mmap().
-Matt
To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-current" in the body of the message
