All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: syzbot <syzbot+d21e6e297322a900c128@syzkaller.appspotmail.com>
Cc: weiyj.lk@gmail.com, kvm@vger.kernel.org, netdev@vger.kernel.org,
	syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: Re: INFO: task hung in vhost_net_stop_vq
Date: Mon, 25 Mar 2019 10:02:43 -0400	[thread overview]
Message-ID: <20190325100223-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <0000000000008ee87005847fc985@google.com>

Looks like more iotlb locking mess?

On Tue, Mar 19, 2019 at 10:21:00PM -0700, syzbot wrote:
> syzbot has bisected this bug to:
> 
> commit 6b1e6cc7855b09a0a9bfa1d9f30172ba366f161c
> Author: Jason Wang <jasowang@redhat.com>
> Date:   Thu Jun 23 06:04:32 2016 +0000
> 
>     vhost: new device IOTLB API
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1486ad27200000
> start commit:   6b1e6cc7 vhost: new device IOTLB API
> git tree:       upstream
> final crash:    https://syzkaller.appspot.com/x/report.txt?x=1686ad27200000
> console output: https://syzkaller.appspot.com/x/log.txt?x=1286ad27200000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=c94f9f0c0363db4b
> dashboard link: https://syzkaller.appspot.com/bug?extid=d21e6e297322a900c128
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=141db34d400000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=108ef293400000
> 
> Reported-by: syzbot+d21e6e297322a900c128@syzkaller.appspotmail.com
> Fixes: 6b1e6cc7 ("vhost: new device IOTLB API")

WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: syzbot <syzbot+d21e6e297322a900c128@syzkaller.appspotmail.com>
Cc: jasowang@redhat.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	syzkaller-bugs@googlegroups.com,
	virtualization@lists.linux-foundation.org, weiyj.lk@gmail.com
Subject: Re: INFO: task hung in vhost_net_stop_vq
Date: Mon, 25 Mar 2019 10:02:43 -0400	[thread overview]
Message-ID: <20190325100223-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <0000000000008ee87005847fc985@google.com>

Looks like more iotlb locking mess?

On Tue, Mar 19, 2019 at 10:21:00PM -0700, syzbot wrote:
> syzbot has bisected this bug to:
> 
> commit 6b1e6cc7855b09a0a9bfa1d9f30172ba366f161c
> Author: Jason Wang <jasowang@redhat.com>
> Date:   Thu Jun 23 06:04:32 2016 +0000
> 
>     vhost: new device IOTLB API
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1486ad27200000
> start commit:   6b1e6cc7 vhost: new device IOTLB API
> git tree:       upstream
> final crash:    https://syzkaller.appspot.com/x/report.txt?x=1686ad27200000
> console output: https://syzkaller.appspot.com/x/log.txt?x=1286ad27200000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=c94f9f0c0363db4b
> dashboard link: https://syzkaller.appspot.com/bug?extid=d21e6e297322a900c128
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=141db34d400000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=108ef293400000
> 
> Reported-by: syzbot+d21e6e297322a900c128@syzkaller.appspotmail.com
> Fixes: 6b1e6cc7 ("vhost: new device IOTLB API")

  reply	other threads:[~2019-03-25 14:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-30 22:32 INFO: task hung in vhost_net_stop_vq syzbot
2019-03-20  5:21 ` syzbot
2019-03-25 14:02   ` Michael S. Tsirkin [this message]
2019-03-25 14:02     ` Michael S. Tsirkin
2019-03-26 10:17     ` Jason Wang
2019-03-26 10:28       ` Dmitry Vyukov
2019-04-09  3:31         ` Jason Wang
2019-04-09  3:31         ` Jason Wang
2019-03-26 10:28       ` Dmitry Vyukov via Virtualization
2019-03-26 10:17     ` Jason Wang

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=20190325100223-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=syzbot+d21e6e297322a900c128@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=weiyj.lk@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.