All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+0abd373e2e50d704db87@syzkaller.appspotmail.com>
To: jasowang@redhat.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, mail@anirudhrb.com, mst@redhat.com,
	netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	virtualization@lists.linux-foundation.org
Subject: Re: [syzbot] INFO: task hung in vhost_work_dev_flush
Date: Mon, 21 Feb 2022 10:40:08 -0800	[thread overview]
Message-ID: <000000000000d6dbd305d88b8fb6@google.com> (raw)
In-Reply-To: <YhPZf7qHeOWHgTHe@anirudhrb.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+0abd373e2e50d704db87@syzkaller.appspotmail.com

Tested on:

commit:         038101e6 Merge tag 'platform-drivers-x86-v5.17-3' of g..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=96b2c57ab158898c
dashboard link: https://syzkaller.appspot.com/bug?extid=0abd373e2e50d704db87
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch:          https://syzkaller.appspot.com/x/patch.diff?x=15e55046700000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2022-02-21 18:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18 23:23 [syzbot] INFO: task hung in vhost_work_dev_flush syzbot
2022-02-21  8:15 ` Anirudh Rayabharam
2022-02-21 14:12 ` Stefano Garzarella
2022-02-21 14:12   ` Stefano Garzarella
2022-02-21 14:37   ` syzbot
2022-02-21 15:53   ` Anirudh Rayabharam
2022-02-21 16:39     ` Stefano Garzarella
2022-02-21 16:39       ` Stefano Garzarella
2022-02-22 10:05     ` Dan Carpenter
2022-02-22 10:05       ` Dan Carpenter
2022-02-22 11:34       ` Anirudh Rayabharam
2022-02-21 18:27 ` Anirudh Rayabharam
2022-02-21 18:40   ` syzbot [this message]
     [not found] <20220219081631.592-1-hdanton@sina.com>
2022-02-19  8:32 ` syzbot

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=000000000000d6dbd305d88b8fb6@google.com \
    --to=syzbot+0abd373e2e50d704db87@syzkaller.appspotmail.com \
    --cc=jasowang@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@anirudhrb.com \
    --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 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.