From: Hillf Danton <hdanton@sina.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: syzbot <syzbot+7f3bbe59e8dd2328a990@syzkaller.appspotmail.com>,
jasowang@redhat.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
Mike Christie <michael.christie@oracle.com>,
stefanha@redhat.com
Subject: Re: [syzbot] [kvm?] [net?] [virt?] INFO: task hung in __vhost_worker_flush
Date: Mon, 1 Sep 2025 18:30:42 +0800 [thread overview]
Message-ID: <20250901103043.6331-1-hdanton@sina.com> (raw)
In-Reply-To: <20240816141505-mutt-send-email-mst@kernel.org>
On Fri, 16 Aug 2024 14:17:30 -0400 "Michael S. Tsirkin" wrote:
>
> Must be this patchset:
>
> https://lore.kernel.org/all/20240316004707.45557-1-michael.christie@oracle.com/
>
> but I don't see anything obvious there to trigger it, and it's not
> reproducible yet...
Mike looks innocent as commit 3652117f8548 failed to survive the syzbot test [1]
[1] https://lore.kernel.org/lkml/68b55f67.050a0220.3db4df.01bf.GAE@google.com/
next prev parent reply other threads:[~2025-09-01 10:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 22:08 syzbot
2024-08-16 18:06 ` Sean Christopherson
2024-08-16 18:06 ` syzbot
2024-08-16 18:10 ` Sean Christopherson
2024-08-16 18:17 ` Michael S. Tsirkin
2024-08-19 15:19 ` Mike Christie
2025-03-27 11:21 ` Stefano Garzarella
2025-09-01 10:30 ` Hillf Danton [this message]
2025-09-01 11:07 ` Michael S. Tsirkin
2025-08-31 2:21 ` [syzbot] [net] [virt] " syzbot
2025-08-31 5:53 ` Hillf Danton
2025-08-31 6:29 ` syzbot
2025-08-31 7:34 ` Hillf Danton
2025-08-31 8:17 ` syzbot
2025-08-31 8:41 ` Hillf Danton
2025-08-31 9:14 ` syzbot
2025-09-01 1:37 ` Hillf Danton
2025-09-01 2:46 ` syzbot
2025-09-01 6:57 ` Hillf Danton
2025-09-01 8:55 ` syzbot
2025-08-31 12:09 ` Forwarded: " syzbot
2025-08-31 15:53 ` 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=20250901103043.6331-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.christie@oracle.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=syzbot+7f3bbe59e8dd2328a990@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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
all inboxes | Powered by JetHome®