Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
	netdev@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
	Hillf Danton <hdanton@sina.com>,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: Reminder: 2 open syzbot bugs in vhost subsystem
Date: Tue, 2 Jul 2019 15:18:25 +0800	[thread overview]
Message-ID: <984f559f-3cfd-cfa5-c37f-272beb58aae1@redhat.com> (raw)
In-Reply-To: <20190702053223.GA27702@sol.localdomain>


On 2019/7/2 下午1:32, Eric Biggers wrote:
> 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@syzkaller.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


Thanks for the hint.

Let me try to invalidate it in the original thread.



      reply	other threads:[~2019-07-02  7:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-02  5:17 Reminder: 2 open syzbot bugs in vhost subsystem Eric Biggers
2019-07-02  5:24 ` Jason Wang
2019-07-02  5:32   ` Eric Biggers
2019-07-02  7:18     ` Jason Wang [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=984f559f-3cfd-cfa5-c37f-272beb58aae1@redhat.com \
    --to=jasowang@redhat.com \
    --cc=ebiggers@kernel.org \
    --cc=hdanton@sina.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