search for: gd683b96

Displaying 6 results from an estimated 6 matches for "gd683b96".

2013 Jun 04
2
vhost && kernel BUG at /build/linux/mm/slub.c:3352!
Hello, Hit this right after killing trinity with Ctrl-C. Was fuzzing v3.10-rc4-0-gd683b96 in a qemu virtual machine as the root user. Tommi [29175] Random reseed: 3970521611 [29175] Random reseed: 202886419 [29175] Random reseed: 2930978521 [179904.099501] binder: 29175:2539 ioctl 4010630e fff returned -22 [29175] Random reseed: 2776471322 [29175] Random reseed: 3086119361 child 2606...
2013 Jun 04
2
vhost && kernel BUG at /build/linux/mm/slub.c:3352!
Hello, Hit this right after killing trinity with Ctrl-C. Was fuzzing v3.10-rc4-0-gd683b96 in a qemu virtual machine as the root user. Tommi [29175] Random reseed: 3970521611 [29175] Random reseed: 202886419 [29175] Random reseed: 2930978521 [179904.099501] binder: 29175:2539 ioctl 4010630e fff returned -22 [29175] Random reseed: 2776471322 [29175] Random reseed: 3086119361 child 2606...
2013 Jun 05
1
vhost && kernel BUG at /build/linux/mm/slub.c:3352!
2013/6/5 Michael S. Tsirkin <mst at redhat.com>: > On Tue, Jun 04, 2013 at 09:50:59PM +0300, Tommi Rantala wrote: >> Hello, >> >> Hit this right after killing trinity with Ctrl-C. Was fuzzing >> v3.10-rc4-0-gd683b96 in a qemu virtual machine as the root user. >> >> Tommi > > Thanks a lot for the report. If found some bugs when looking > at this: I think they were introduced by > 2839400f8fe28ce216eeeba3fb97bdf90977f7ad > though I don't exactly see how ctrl-c can trigger this. &gt...
2013 Jun 05
1
vhost && kernel BUG at /build/linux/mm/slub.c:3352!
2013/6/5 Michael S. Tsirkin <mst at redhat.com>: > On Tue, Jun 04, 2013 at 09:50:59PM +0300, Tommi Rantala wrote: >> Hello, >> >> Hit this right after killing trinity with Ctrl-C. Was fuzzing >> v3.10-rc4-0-gd683b96 in a qemu virtual machine as the root user. >> >> Tommi > > Thanks a lot for the report. If found some bugs when looking > at this: I think they were introduced by > 2839400f8fe28ce216eeeba3fb97bdf90977f7ad > though I don't exactly see how ctrl-c can trigger this. &gt...
2013 Jun 05
0
vhost && kernel BUG at /build/linux/mm/slub.c:3352!
...M +0300, Tommi Rantala wrote: > 2013/6/5 Michael S. Tsirkin <mst at redhat.com>: > > On Tue, Jun 04, 2013 at 09:50:59PM +0300, Tommi Rantala wrote: > >> Hello, > >> > >> Hit this right after killing trinity with Ctrl-C. Was fuzzing > >> v3.10-rc4-0-gd683b96 in a qemu virtual machine as the root user. > >> > >> Tommi > > > > Thanks a lot for the report. If found some bugs when looking > > at this: I think they were introduced by > > 2839400f8fe28ce216eeeba3fb97bdf90977f7ad > > though I don't exactly s...
2013 Jun 05
0
vhost && kernel BUG at /build/linux/mm/slub.c:3352!
On Tue, Jun 04, 2013 at 09:50:59PM +0300, Tommi Rantala wrote: > Hello, > > Hit this right after killing trinity with Ctrl-C. Was fuzzing > v3.10-rc4-0-gd683b96 in a qemu virtual machine as the root user. > > Tommi Thanks a lot for the report. If found some bugs when looking at this: I think they were introduced by 2839400f8fe28ce216eeeba3fb97bdf90977f7ad though I don't exactly see how ctrl-c can trigger this. I'll work on patches - is this...