From: "Michael S. Tsirkin" <mst@redhat.com>
To: Mike Christie <michael.christie@oracle.com>
Cc: virtualization@lists.linux-foundation.org, stefanha@redhat.com
Subject: Re: vhost: Fix vhost_task regressions in 6.4-rc
Date: Wed, 7 Jun 2023 16:22:33 -0400 [thread overview]
Message-ID: <20230607162028-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230607192338.6041-1-michael.christie@oracle.com>
On Wed, Jun 07, 2023 at 02:23:36PM -0500, Mike Christie wrote:
> The following patches were made over Linus's tree which contains a
> vhost change missing in mst's vhost branch. These patches fix two
> issues caused by the vhost_task patches:
> 1. I was setting dev->worker too early and this caused crashes when
> vsock would queue work before VHOST_SET_OWNER.
>
> 2. The patch that Linus's tree contains which vhost does not yet
> have converted vhost_tasks to use CLONE_THREAD. That required a
> change to how we set the task state, but I completely messed up
> and moved when we set ourself to interruptible too late.
>
Right. and that's in rc5 yes?
--
MST
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2023-06-07 20:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 19:23 vhost: Fix vhost_task regressions in 6.4-rc Mike Christie
2023-06-07 19:23 ` [PATCH 1/2] vhost: Fix crash during early vhost_transport_send_pkt calls Mike Christie
2023-06-08 8:39 ` Stefano Garzarella
2023-06-08 15:11 ` Michael S. Tsirkin
2023-06-07 19:23 ` [PATCH 2/2] vhost: Fix worker hangs due to missed wake up calls Mike Christie
2023-06-07 20:22 ` Michael S. Tsirkin [this message]
2023-06-08 0:38 ` vhost: Fix vhost_task regressions in 6.4-rc Mike Christie
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=20230607162028-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=michael.christie@oracle.com \
--cc=stefanha@redhat.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).