From: Dan Carpenter <dan.carpenter@oracle.com>
To: Anirudh Rayabharam <mail@anirudhrb.com>
Cc: kvm <kvm@vger.kernel.org>, Michael Tsirkin <mst@redhat.com>,
netdev <netdev@vger.kernel.org>,
syzkaller-bugs@googlegroups.com,
kernel list <linux-kernel@vger.kernel.org>,
Linux Virtualization <virtualization@lists.linux-foundation.org>,
syzbot <syzbot+0abd373e2e50d704db87@syzkaller.appspotmail.com>
Subject: Re: [syzbot] INFO: task hung in vhost_work_dev_flush
Date: Tue, 22 Feb 2022 13:05:56 +0300 [thread overview]
Message-ID: <20220222100556.GM3965@kadam> (raw)
In-Reply-To: <YhO1YL0A6OjtXmIy@anirudhrb.com>
On Mon, Feb 21, 2022 at 09:23:04PM +0530, Anirudh Rayabharam wrote:
> On Mon, Feb 21, 2022 at 03:12:33PM +0100, Stefano Garzarella wrote:
> > #syz test: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
> > f71077a4d84b
> >
> > Patch sent upstream:
> > https://lore.kernel.org/virtualization/20220221114916.107045-1-sgarzare@redhat.com/T/#u
>
> I don't see how your patch fixes this issue. It looks unrelated. It is
> surprising that syzbot is happy with it.
>
> I have sent a patch for this issue here:
> https://lore.kernel.org/lkml/20220221072852.31820-1-mail@anirudhrb.com/
I wasted so much time trying to figure out what this patch fixes. :P
(It doesn't fix anything).
regards,
dan carpenter
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
prev parent reply other threads:[~2022-02-22 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000057702a05d8532b18@google.com>
2022-02-21 14:12 ` [syzbot] INFO: task hung in vhost_work_dev_flush Stefano Garzarella
[not found] ` <YhO1YL0A6OjtXmIy@anirudhrb.com>
2022-02-21 16:39 ` Stefano Garzarella
2022-02-22 10:05 ` Dan Carpenter [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=20220222100556.GM3965@kadam \
--to=dan.carpenter@oracle.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=syzbot+0abd373e2e50d704db87@syzkaller.appspotmail.com \
--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).