netdev - Re: Reminder: 2 open syzbot bugs in vhost subsystem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 1 Jul 2019 22:32:23 -0700
From:   Eric Biggers <ebiggers@...nel.org>
To:     Jason Wang <jasowang@...hat.com>
Cc:     kvm@...r.kernel.org, virtualization@...ts.linux-foundation.org,
        netdev@...r.kernel.org, "Michael S. Tsirkin" <mst@...hat.com>,
        Hillf Danton <hdanton@...a.com>, linux-kernel@...r.kernel.org,
        syzkaller-bugs@...glegroups.com
Subject: Re: Reminder: 2 open syzbot bugs in vhost subsystem

On Tue, Jul 02, 2019 at 01:24:43PM +0800, Jason Wang wrote:
> > --------------------------------------------------------------------------------
> > Title:              INFO: task hung in vhost_init_device_iotlb
> > Last occurred:      125 days ago
> > Reported:           153 days ago
> > Branches:           Mainline and others
> > Dashboard link:     https://syzkaller.appspot.com/bug?id=cb1ea8daf03a5942c2ab314679148cf6e128ef58
> > Original thread:    https://lkml.kernel.org/lkml/0000000000007e86fd058095533f@google.com/T/#u
> > 
> > Unfortunately, this bug does not have a reproducer.
> > 
> > The original thread for this bug received 2 replies; the last was 152 days ago.
> > 
> > If you fix this bug, please add the following tag to the commit:
> >      Reported-by: syzbot+40e28a8bd59d10ed0c42@...kaller.appspotmail.com
> > 
> > If you send any email or patch for this bug, please consider replying 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/0000000000007e86fd058095533f@google.com
> > 
> 
> Can syzbot still reproduce this issue?

Apparently not, as it last occurred 125 days ago.

That doesn't necessarily mean the bug isn't still there, though.

But if you (as a person familiar with the code) think it's no longer valid or
not actionable, you can invalidate it.

- Eric