[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220222100556.GM3965@kadam>
Date: Tue, 22 Feb 2022 13:05:56 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Anirudh Rayabharam <mail@...rudhrb.com>
Cc: Stefano Garzarella <sgarzare@...hat.com>,
syzbot <syzbot+0abd373e2e50d704db87@...kaller.appspotmail.com>,
Jason Wang <jasowang@...hat.com>, kvm <kvm@...r.kernel.org>,
kernel list <linux-kernel@...r.kernel.org>,
Michael Tsirkin <mst@...hat.com>,
netdev <netdev@...r.kernel.org>, syzkaller-bugs@...glegroups.com,
Linux Virtualization <virtualization@...ts.linux-foundation.org>
Subject: Re: [syzbot] INFO: task hung in vhost_work_dev_flush
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
Powered by blists - more mailing lists