From: Mike Christie <michael.christie@oracle.com>
To: Jason Wang <jasowang@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: Cindy Lu <lulu@redhat.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [RESEND PATCH v1 0/7]vhost: Add support of kthread API
Date: Wed, 11 Sep 2024 11:17:12 -0500 [thread overview]
Message-ID: <94c76200-05b2-4142-a637-bf2115827116@oracle.com> (raw)
In-Reply-To: <CACGkMEv71_eUY_2361TNKhTxqxnR4iTyOXq6aKR_6MqaxqM5Dg@mail.gmail.com>
On 9/10/24 10:45 PM, Jason Wang wrote:
>>> It depends on how we define "secure". There's plenty of users of
>>> kthread and if I was not wrong, mike may still need to fix some bugs.
>>>
>>
>> which bugs?
>
> https://lore.kernel.org/all/06369c2c-c363-4def-9ce0-f018a9e10e8d@oracle.com/T/
The SIGKILL issue in that specific email is fixed. The patches are
merged upstream. I don't know of any other bugs like that (crashes,
hangs, etc). There is the one we can't reproduce so are not sure if
it's the vhost changes.
There is the change in behavior type of bug we discussed in that
thread:
https://lore.kernel.org/all/06369c2c-c363-4def-9ce0-f018a9e10e8d@oracle.com/T/#m026f7dd96e064e3a604155e45e7ae9d5c949ae23
next prev parent reply other threads:[~2024-09-11 16:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 2:00 Cindy Lu
2024-09-09 2:00 ` [RESEND PATCH v1 1/7] vhost: Add a new module_param for enable kthread Cindy Lu
2024-09-10 5:12 ` kernel test robot
2024-09-09 2:00 ` [RESEND PATCH v1 2/7] vhost: Add kthread support in function vhost_worker_queue() Cindy Lu
2024-09-09 2:00 ` [RESEND PATCH v1 3/7] vhost: Add kthread support in function vhost_workers_free() Cindy Lu
2024-09-09 2:00 ` [RESEND PATCH v1 4/7] vhost: Add the vhost_worker to support kthread Cindy Lu
2024-09-09 2:00 ` [RESEND PATCH v1 5/7] vhost: Add the cgroup related function Cindy Lu
2024-09-09 2:00 ` [RESEND PATCH v1 6/7] vhost: Add kthread support in function vhost_worker_create Cindy Lu
2024-09-09 2:00 ` [RESEND PATCH v1 7/7] vhost: Add new UAPI to support change to task mode Cindy Lu
2024-09-10 7:41 ` [RESEND PATCH v1 0/7]vhost: Add support of kthread API Michael S. Tsirkin
2024-09-10 8:37 ` Jason Wang
2024-09-10 8:42 ` Michael S. Tsirkin
2024-09-11 3:45 ` Jason Wang
2024-09-11 10:28 ` Michael S. Tsirkin
2024-09-11 16:17 ` Mike Christie [this message]
[not found] ` <CACGkMEvAR_2j=PdKZZyAZ1yK7H5OO+Ldc0Eygwyo8rMR=_uGBQ@mail.gmail.com>
2024-09-23 1:15 ` Cindy Lu
2024-09-11 16:20 ` Mike Christie
2024-09-11 19:02 ` Michael S. Tsirkin
2024-09-12 1:47 ` Jason Wang
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=94c76200-05b2-4142-a637-bf2115827116@oracle.com \
--to=michael.christie@oracle.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=mst@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
all inboxes | Powered by JetHome®