[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220221140453.ndai2piyhrs3y5jw@sgarzare-redhat>
Date: Mon, 21 Feb 2022 15:04:53 +0100
From: Stefano Garzarella <sgarzare@...hat.com>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: Hillf Danton <hdanton@...a.com>,
syzbot <syzbot+3140b17cb44a7b174008@...kaller.appspotmail.com>,
jasowang@...hat.com, linux-kernel@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] kernel BUG in vhost_get_vq_desc
On Mon, Feb 21, 2022 at 08:59:56AM -0500, Michael S. Tsirkin wrote:
>On Mon, Feb 21, 2022 at 02:45:16PM +0100, Stefano Garzarella wrote:
>> On Mon, Feb 21, 2022 at 09:36:46PM +0800, Hillf Danton wrote:
>> > Hey Stefano,
>> >
>> > On Mon, 21 Feb 2022 14:09:26 +0100 Stefano Garzarella wrote:
>> > > It seems that this patch [1] should fix also this issue. (syzbot seems
>> > > happy).
>> >
>> > What do you mean by happy?
>> > Why not feed it to syzbot if it is a good fix, given a test-by tag can
>> > speak for itself?
>>
>> Because I sent the patch this morning for another report:
>> https://syzkaller.appspot.com/bug?extid=1e3ea63db39f2b4440e0
>>
>> Then I asked syzbot for this report to test my branch with that patch
>> applied and the result is OK.
>>
>> Is there any way to ask syzbot to test a patch already posted to the mailing
>> list? (instead of sending it back to it again)
>>
>> Stefano
>
>I don't know of a way, but hey, sending it back isn't too bad,
>just mention this in the mail text.
>
Okay, I'll do also for another report.
Thanks,
Stefano
Powered by blists - more mailing lists