On Wed, Oct 02, 2013 at 01:44:44PM -0700, Ildar Muslukhov wrote:
> That's what I though as well. However, just encountered segfaults on
> x64 read syscall. Although this one might be legit.
in case you didn't realise, there's a few cases where we expect to segfault.
for eg, if we mprotect page_rand to PROT_NONE and then something tries to read
it.
There's a whole bunch of similar gotchas. I've special cased the sanitise
routines
of some syscalls to avoid this sort of thing, but there's a few cases where
a trinity child will corrupt itself. It then dies, and respawns, so I haven't
really
worried too much about it.
Dave
--
To unsubscribe from this list: send the line "unsubscribe trinity" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
