All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Hillf Danton <hdanton@sina.com>,
	syzbot <syzbot+3140b17cb44a7b174008@syzkaller.appspotmail.com>,
	jasowang@redhat.com, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] kernel BUG in vhost_get_vq_desc
Date: Mon, 21 Feb 2022 08:59:56 -0500	[thread overview]
Message-ID: <20220221085926-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220221134516.gmm3a5bjdlnzile2@sgarzare-redhat>

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.


  reply	other threads:[~2022-02-21 14:00 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 [this message]
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
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=20220221085926-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=hdanton@sina.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sgarzare@redhat.com \
    --cc=syzbot+3140b17cb44a7b174008@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 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.