kernel version 3.8.4 crashed while fuzzying with trinity
From: Toralf FÃrster
Date: Sat Mar 23 2013 - 14:44:01 EST
That kernel crashed today at a stable 32 bit Gentoo Linux.
The screen shot (just a photo, b/c nothing was in the syslog) can be downloaded here .
The last action before I left the machine for a while was to start a user mode linux
(stale 32 bit Gentoo, kernel v3.9-rc3-324-g5da273) and run trinity within that system.
Please note that the host kernel crashed (UML probably too).
To feed trinity with victim files I NFSv4 mounted a directory located at the host system
under /tmp onto a mount point of the UML system (all file systems are EXT4).
That directory contained 100 files and 100 directory.
The trinity command line I used in the UML was :
$> trinity --children 4 --victims /mnt/nfs/n22/forT -x mremap -x clock_nanosleep
FWIW : mremap gives within an UML guest with kernel 3.9-rcX this  using SLAB
and with SLUB this ;
clock_nanosleep only slows down the tests
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/