All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+a61bac2fcc1a7c6623fe@syzkaller.appspotmail.com>
To: davem@davemloft.net, decui@microsoft.com, jhansen@vmware.com,
	kuba@kernel.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	sgarzare@redhat.com, stefanha@redhat.com,
	syzkaller-bugs@googlegroups.com,
	virtualization@lists.linux-foundation.org
Subject: Re: general protection fault in vsock_poll
Date: Wed, 29 Jul 2020 01:59:05 -0700	[thread overview]
Message-ID: <00000000000093b5dc05ab90c468@google.com> (raw)
In-Reply-To: <00000000000099052605aafb5923@google.com>

syzbot has bisected this issue to:

commit 408624af4c89989117bb2c6517bd50b7708a2fcd
Author: Stefano Garzarella <sgarzare@redhat.com>
Date:   Tue Dec 10 10:43:06 2019 +0000

    vsock: use local transport when it is loaded

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17e6489b100000
start commit:   92ed3019 Linux 5.8-rc7
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=1416489b100000
console output: https://syzkaller.appspot.com/x/log.txt?x=1016489b100000
kernel config:  https://syzkaller.appspot.com/x/.config?x=84f076779e989e69
dashboard link: https://syzkaller.appspot.com/bug?extid=a61bac2fcc1a7c6623fe
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15930b64900000

Reported-by: syzbot+a61bac2fcc1a7c6623fe@syzkaller.appspotmail.com
Fixes: 408624af4c89 ("vsock: use local transport when it is loaded")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  reply	other threads:[~2020-07-29  8:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 22:43 general protection fault in vsock_poll syzbot
2020-07-29  8:59 ` syzbot [this message]
2020-07-29  9:40   ` Stefano Garzarella

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=00000000000093b5dc05ab90c468@google.com \
    --to=syzbot+a61bac2fcc1a7c6623fe@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=decui@microsoft.com \
    --cc=jhansen@vmware.com \
    --cc=kuba@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=syzkaller-bugs@googlegroups.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 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.