linux-kernel - Re: vhost && kernel BUG at /build/linux/mm/slub.c:3352!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20130605120850.GA3410@redhat.com>
Date:	Wed, 5 Jun 2013 15:08:50 +0300
From:	"Michael S. Tsirkin" <mst@...hat.com>
To:	Tommi Rantala <tt.rantala@...il.com>
Cc:	kvm@...r.kernel.org, virtualization@...ts.linux-foundation.org,
	trinity@...r.kernel.org, netdev@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>,
	Dave Jones <davej@...hat.com>
Subject: Re: 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@...hat.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

Great, I'll post patches and we can see if it's fixed.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/