From: "Michael S. Tsirkin" <mst@redhat.com>
To: Tommi Rantala <tt.rantala@gmail.com>
Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
trinity@vger.kernel.org, netdev@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>
Subject: Re: vhost && kernel BUG at /build/linux/mm/slub.c:3352!
Date: Wed, 5 Jun 2013 15:08:50 +0300 [thread overview]
Message-ID: <20130605120850.GA3410@redhat.com> (raw)
In-Reply-To: <CA+ydwtq6FNSXhjGuqtQBUKVQJNOD_iKWpnUqj4rbfQJTkw+bog@mail.gmail.com>
On Wed, Jun 05, 2013 at 03:06:33PM +0300, Tommi Rantala wrote:
> 2013/6/5 Michael S. Tsirkin <mst@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
Great, I'll post patches and we can see if it's fixed.
prev parent reply other threads:[~2013-06-05 12:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 18:50 vhost && kernel BUG at /build/linux/mm/slub.c:3352! Tommi Rantala
2013-06-05 11:54 ` Michael S. Tsirkin
2013-06-05 12:06 ` Tommi Rantala
2013-06-05 12:08 ` Michael S. Tsirkin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130605120850.GA3410@redhat.com \
--to=mst@redhat.com \
--cc=davej@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=trinity@vger.kernel.org \
--cc=tt.rantala@gmail.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).