On Sun, Aug 03, 2014 at 03:52:18PM +0200, Toralf Förster wrote:
> Hello,
>
> fuzzying a 32 bit stable Gentoo x86 linux with trinity (and without excluding
> the munmap syscall but it might be independed from this) gives within a 32
> bit user mode linux guest :
The problem with these sorts of trinity bug reports is that we have no
idea which syscall or set of syscalls might have corrupted kernel
state to the point where the kernel started malfunctioning.
Sometimes, a trinity induced bug is obvious, when it causes a system
call to immediately access an illegal memory location. But if it
causes some more subtle corruption, possibly in a completely unrelated
subsystem, figuring out what actually happened can be close to
impossible.
So there's not much I can do with this sort of bug report. If you can
easily repeat it, and you can dump out the system call stream, we
might be able to make a smaller reproduction case, at which point
trying to debug this sort of failure would be tractable.
Cheers,
- Ted
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
