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. > I'll work on patches - is this reproducible at all?Thanks, glad to hear that the report was useful. Yes, I did reproduce this quite quickly yesterday with trinity, but did not dig any deeper into what was going on. Tommi
Michael S. Tsirkin
2013-Jun-05 12:08 UTC
vhost && kernel BUG at /build/linux/mm/slub.c:3352!
On Wed, Jun 05, 2013 at 03:06:33PM +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 see how ctrl-c can trigger this. > > I'll work on patches - is this reproducible at all? > > Thanks, glad to hear that the report was useful. > > Yes, I did reproduce this quite quickly yesterday with trinity, but > did not dig any deeper into what was going on. > > TommiGreat, I'll post patches and we can see if it's fixed.
Reasonably Related Threads
- vhost && kernel BUG at /build/linux/mm/slub.c:3352!
- vhost && kernel BUG at /build/linux/mm/slub.c:3352!
- vhost && kernel BUG at /build/linux/mm/slub.c:3352!
- vhost && kernel BUG at /build/linux/mm/slub.c:3352!
- vhost && kernel BUG at /build/linux/mm/slub.c:3352!