From: syzbot <syzbot+3140b17cb44a7b174008@syzkaller.appspotmail.com>
To: hdanton@sina.com, jasowang@redhat.com,
linux-kernel@vger.kernel.org, mst@redhat.com,
sgarzare@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] kernel BUG in vhost_get_vq_desc
Date: Mon, 21 Feb 2022 06:25:07 -0800 [thread overview]
Message-ID: <000000000000cde22e05d887fff4@google.com> (raw)
In-Reply-To: <CAGxU2F4f0Gx=-4g-r3QHFPsn0WwSW3HyT+MRKj4=TTWp9R+WYw@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+3140b17cb44a7b174008@syzkaller.appspotmail.com
Tested on:
commit: f71077a4 Merge tag 'mmc-v5.17-rc1-2' of git://git.kern..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
kernel config: https://syzkaller.appspot.com/x/.config?x=a78b064590b9f912
dashboard link: https://syzkaller.appspot.com/bug?extid=3140b17cb44a7b174008
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=123f7296700000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2022-02-21 14:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220219125100.835-1-hdanton@sina.com>
2022-02-19 13:01 ` [syzbot] kernel BUG in vhost_get_vq_desc syzbot
2022-02-21 13:09 ` Stefano Garzarella
[not found] ` <20220221133646.1551-1-hdanton@sina.com>
2022-02-21 13:45 ` Stefano Garzarella
2022-02-21 13:59 ` Michael S. Tsirkin
2022-02-21 14:04 ` Stefano Garzarella
[not found] ` <20220220014715.921-1-hdanton@sina.com>
2022-02-20 2:10 ` syzbot
2022-02-21 14:09 ` Stefano Garzarella
2022-02-21 14:25 ` syzbot [this message]
2022-02-20 10:08 ` Michael S. Tsirkin
[not found] ` <20220220110941.980-1-hdanton@sina.com>
2022-02-20 12:16 ` Michael S. Tsirkin
2022-02-20 12:31 ` Dmitry Vyukov
2022-02-20 13:10 ` Michael S. Tsirkin
2022-02-20 13:29 ` Michael S. Tsirkin
2022-02-20 13:20 ` syzbot
[not found] <20220222031128.1850-1-hdanton@sina.com>
2022-02-22 4:07 ` syzbot
[not found] <20220222001455.1737-1-hdanton@sina.com>
2022-02-22 0:26 ` syzbot
[not found] <20220221140558.1618-1-hdanton@sina.com>
2022-02-21 14:14 ` syzbot
[not found] <20220221054115.1270-1-hdanton@sina.com>
2022-02-21 5:51 ` syzbot
[not found] <20220221040745.1177-1-hdanton@sina.com>
2022-02-21 4:18 ` syzbot
[not found] ` <20220221085227.1356-1-hdanton@sina.com>
2022-02-21 9:17 ` Michael S. Tsirkin
[not found] ` <20220221101538.1415-1-hdanton@sina.com>
2022-02-21 10:48 ` Michael S. Tsirkin
[not found] ` <20220221130022.1494-1-hdanton@sina.com>
2022-02-21 13:58 ` Michael S. Tsirkin
2022-02-21 12:46 ` syzbot
[not found] <20220221021208.1109-1-hdanton@sina.com>
2022-02-21 2:26 ` syzbot
[not found] <20220219114936.747-1-hdanton@sina.com>
2022-02-19 12:00 ` syzbot
2022-02-12 22:47 syzbot
2022-02-18 1:21 ` syzbot
2022-02-18 11:37 ` Michael S. Tsirkin
2022-02-18 11:37 ` Michael S. Tsirkin
2022-03-02 8:29 ` Lee Jones
2022-03-02 8:29 ` Lee Jones
2022-03-02 9:18 ` Stefano Garzarella
2022-03-02 9:18 ` Stefano Garzarella
2022-03-02 9:23 ` Stefano Garzarella
2022-03-02 9:23 ` Stefano Garzarella
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=000000000000cde22e05d887fff4@google.com \
--to=syzbot+3140b17cb44a7b174008@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=sgarzare@redhat.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 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.