From: syzbot <syzbot+30b72abaa17c07fe39dd@syzkaller.appspotmail.com>
To: bobby.eshleman@bytedance.com, bobby.eshleman@gmail.com,
bobbyeshleman@gmail.com, cong.wang@bytedance.com,
deshantm@xen.org, jasowang@redhat.com, jiang.wang@bytedance.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
mst@redhat.com, netdev@vger.kernel.org, oxffffaa@gmail.com,
pabeni@redhat.com, sgarzare@redhat.com, stefanha@redhat.com,
syzkaller-bugs@googlegroups.com,
virtualization@lists.linux-foundation.org,
xiyou.wangcong@gmail.com
Subject: Re: [syzbot] kernel BUG in vhost_vsock_handle_tx_kick
Date: Wed, 04 Jan 2023 20:51:23 -0800 [thread overview]
Message-ID: <0000000000008a2d5305f17d0dbe@google.com> (raw)
In-Reply-To: <0000000000003a68dc05f164fd69@google.com>
syzbot has bisected this issue to:
commit b68396fad17ff7fae3bb5b594d703f7195caebb9
Author: Bobby Eshleman <bobby.eshleman@bytedance.com>
Date: Thu Dec 15 04:36:44 2022 +0000
virtio/vsock: replace virtio_vsock_pkt with sk_buff
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=132ece3a480000
start commit: c76083fac3ba Add linux-next specific files for 20221226
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=10aece3a480000
console output: https://syzkaller.appspot.com/x/log.txt?x=172ece3a480000
kernel config: https://syzkaller.appspot.com/x/.config?x=c217c755f1884ab6
dashboard link: https://syzkaller.appspot.com/bug?extid=30b72abaa17c07fe39dd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14fc414c480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1604b20a480000
Reported-by: syzbot+30b72abaa17c07fe39dd@syzkaller.appspotmail.com
Fixes: b68396fad17f ("virtio/vsock: replace virtio_vsock_pkt with sk_buff")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-01-05 4:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 0:08 [syzbot] kernel BUG in vhost_vsock_handle_tx_kick syzbot
2023-01-04 4:21 ` Cong Wang
2022-12-19 10:46 ` Bobby Eshleman
2023-01-04 13:03 ` Michael S. Tsirkin
2023-01-05 4:51 ` syzbot [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=0000000000008a2d5305f17d0dbe@google.com \
--to=syzbot+30b72abaa17c07fe39dd@syzkaller.appspotmail.com \
--cc=bobby.eshleman@bytedance.com \
--cc=bobby.eshleman@gmail.com \
--cc=bobbyeshleman@gmail.com \
--cc=cong.wang@bytedance.com \
--cc=deshantm@xen.org \
--cc=jasowang@redhat.com \
--cc=jiang.wang@bytedance.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=oxffffaa@gmail.com \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xiyou.wangcong@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 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).