From: Eric Biggers <ebiggers@kernel.org>
To: Jason Wang <jasowang@redhat.com>
Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: Reminder: 3 open syzbot bugs in vhost subsystem
Date: Tue, 23 Jul 2019 20:13:54 -0700 [thread overview]
Message-ID: <20190724031354.GV643@sol.localdomain> (raw)
In-Reply-To: <fabf96ac-e472-c7fd-07ff-486fe03e6433@redhat.com>
On Wed, Jul 24, 2019 at 11:05:14AM +0800, Jason Wang wrote:
> > --------------------------------------------------------------------------------
> > Title: KASAN: use-after-free Write in tlb_finish_mmu
> > Last occurred: 5 days ago
> > Reported: 4 days ago
> > Branches: Mainline
> > Dashboard link: https://syzkaller.appspot.com/bug?id=d57b94f89e48c85ef7d95acc208209ea4bdc10de
> > Original thread: https://lkml.kernel.org/lkml/00000000000045e7a1058e02458a@google.com/T/#u
> >
> > This bug has a syzkaller reproducer only.
> >
> > This bug was bisected to:
> >
> > commit 7f466032dc9e5a61217f22ea34b2df932786bbfc
> > Author: Jason Wang <jasowang@redhat.com>
> > Date: Fri May 24 08:12:18 2019 +0000
> >
> > vhost: access vq metadata through kernel virtual address
> >
> > No one has replied to the original thread for this bug yet.
> >
> > If you fix this bug, please add the following tag to the commit:
> > Reported-by: syzbot+8267e9af795434ffadad@syzkaller.appspotmail.com
> >
> > If you send any email or patch for this bug, please reply to the original
> > thread. For the git send-email command to use, or tips on how to reply if the
> > thread isn't in your mailbox, see the "Reply instructions" at
> > https://lkml.kernel.org/r/00000000000045e7a1058e02458a@google.com
> >
> > --------------------------------------------------------------------------------
> > Title: KASAN: use-after-free Read in finish_task_switch (2)
> > Last occurred: 5 days ago
> > Reported: 4 days ago
> > Branches: Mainline
> > Dashboard link: https://syzkaller.appspot.com/bug?id=9a98fcad6c8bd31f5c3afbdc6c75de9f082c0ffa
> > Original thread: https://lkml.kernel.org/lkml/000000000000490679058e0245ee@google.com/T/#u
> >
> > This bug has a syzkaller reproducer only.
> >
> > This bug was bisected to:
> >
> > commit 7f466032dc9e5a61217f22ea34b2df932786bbfc
> > Author: Jason Wang <jasowang@redhat.com>
> > Date: Fri May 24 08:12:18 2019 +0000
> >
> > vhost: access vq metadata through kernel virtual address
> >
> > No one has replied to the original thread for this bug yet.
>
>
> Hi:
>
> We believe above two bugs are duplicated with the report "WARNING in
> __mmdrop". Can I just dup them with
>
> #syz dup "WARNING in __mmdrop"
>
> (If yes, just wonder how syzbot differ bugs, technically, several different
> bug can hit the same warning).
>
Yes, please mark them as duplicates; see https://goo.gl/tpsmEJ#status for
correct syntax. You need to send the command to the syzbot email address
specific to each bug. Easiest way is to reply to the original threads.
- Eric
prev parent reply other threads:[~2019-07-24 3:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 2:38 Reminder: 3 open syzbot bugs in vhost subsystem Eric Biggers
2019-07-24 3:05 ` Jason Wang
2019-07-24 3:05 ` syzbot
2019-07-24 3:13 ` Eric Biggers [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=20190724031354.GV643@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--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 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).