From: Mike Christie <michael.christie@oracle.com>
To: Stefano Garzarella <sgarzare@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: syzbot <syzbot+d0d442c22fa8db45ff0e@syzkaller.appspotmail.com>,
jasowang@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com,
virtualization@lists.linux-foundation.org, stefanha@redhat.com
Subject: Re: [syzbot] [kvm?] [net?] [virt?] general protection fault in vhost_work_queue
Date: Tue, 30 May 2023 10:58:12 -0500 [thread overview]
Message-ID: <85836a9b-b30a-bdb6-d058-1f7c17d8e48e@oracle.com> (raw)
In-Reply-To: <CAGxU2F7O7ef3mdvNXtiC0VtWiS2DMnoiGwSR=Z6SWbzqcrBF-g@mail.gmail.com>
On 5/30/23 8:44 AM, Stefano Garzarella wrote:
>
> From a first glance, it looks like an issue when we call vhost_work_queue().
> @Mike, does that ring any bells since you recently looked at that code?
I see the bug. needed to have set the dev->worker after setting worker->vtsk
like below:
diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
index a92af08e7864..7bd95984a501 100644
--- a/drivers/vhost/vhost.c
+++ b/drivers/vhost/vhost.c
@@ -564,7 +564,6 @@ static int vhost_worker_create(struct vhost_dev *dev)
if (!worker)
return -ENOMEM;
- dev->worker = worker;
worker->kcov_handle = kcov_common_handle();
init_llist_head(&worker->work_list);
snprintf(name, sizeof(name), "vhost-%d", current->pid);
@@ -576,6 +575,7 @@ static int vhost_worker_create(struct vhost_dev *dev)
}
worker->vtsk = vtsk;
+ dev->worker = worker;
vhost_task_start(vtsk);
return 0;
next prev parent reply other threads:[~2023-05-30 15:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 7:30 [syzbot] [kvm?] [net?] [virt?] general protection fault in vhost_work_queue syzbot
2023-05-30 11:24 ` Michael S. Tsirkin
2023-05-30 13:44 ` Stefano Garzarella
2023-05-30 15:58 ` Mike Christie [this message]
2023-05-30 16:01 ` Mike Christie
2023-05-30 16:11 ` Stefano Garzarella
2023-05-30 16:00 ` Stefano Garzarella
2023-05-30 16:09 ` Mike Christie
2023-05-30 16:17 ` Stefano Garzarella
2023-05-30 16:30 ` michael.christie
2023-05-31 7:27 ` Stefano Garzarella
2023-05-31 15:15 ` Mike Christie
2023-05-31 16:27 ` Mike Christie
2023-06-01 7:47 ` Stefano Garzarella
2023-06-01 16:33 ` Mike Christie
2023-06-05 8:26 ` 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=85836a9b-b30a-bdb6-d058-1f7c17d8e48e@oracle.com \
--to=michael.christie@oracle.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=syzbot+d0d442c22fa8db45ff0e@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).