From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
pbonzini@redhat.com, stefanha@redhat.com
Subject: Re: [PATCH V2 0/4] Prevent vhost kthread from hogging CPU
Date: Mon, 20 May 2019 08:52:59 -0400 [thread overview]
Message-ID: <20190520085207-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1558067392-11740-1-git-send-email-jasowang@redhat.com>
On Fri, May 17, 2019 at 12:29:48AM -0400, Jason Wang wrote:
> Hi:
>
> This series try to prevent a guest triggerable CPU hogging through
> vhost kthread. This is done by introducing and checking the weight
> after each requrest. The patch has been tested with reproducer of
> vsock and virtio-net. Only compile test is done for vhost-scsi.
>
> Please review.
> This addresses CVE-2019-3900.
OK I think we should clean this code some more but given
it's a CVE fix maybe it's best to do as a patch on top.
Acked-by: Michael S. Tsirkin <mst@redhat.com>
Dave do you want to merge this or should I?
>
> Changs from V1:
> - fix user-ater-free in vosck patch
>
> Jason Wang (4):
> vhost: introduce vhost_exceeds_weight()
> vhost_net: fix possible infinite loop
> vhost: vsock: add weight support
> vhost: scsi: add weight support
>
> drivers/vhost/net.c | 41 ++++++++++++++---------------------------
> drivers/vhost/scsi.c | 21 ++++++++++++++-------
> drivers/vhost/vhost.c | 20 +++++++++++++++++++-
> drivers/vhost/vhost.h | 5 ++++-
> drivers/vhost/vsock.c | 28 +++++++++++++++++++++-------
> 5 files changed, 72 insertions(+), 43 deletions(-)
>
> --
> 1.8.3.1
next prev parent reply other threads:[~2019-05-20 12:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 4:29 [PATCH V2 0/4] Prevent vhost kthread from hogging CPU Jason Wang
2019-05-17 4:29 ` [PATCH V2 1/4] vhost: introduce vhost_exceeds_weight() Jason Wang
2019-05-17 4:29 ` Jason Wang
2019-05-17 4:29 ` [PATCH V2 2/4] vhost_net: fix possible infinite loop Jason Wang
2019-05-17 4:29 ` Jason Wang
2019-05-17 4:29 ` [PATCH V2 3/4] vhost: vsock: add weight support Jason Wang
2019-05-17 4:29 ` Jason Wang
2019-05-17 4:29 ` [PATCH V2 4/4] vhost: scsi: " Jason Wang
2019-05-17 4:29 ` Jason Wang
2019-05-17 9:10 ` [PATCH V2 0/4] Prevent vhost kthread from hogging CPU Stefan Hajnoczi
2019-05-17 9:10 ` Stefan Hajnoczi
2019-05-18 20:27 ` David Miller
2019-05-18 20:27 ` David Miller
2019-05-23 17:22 ` Michael S. Tsirkin
2019-05-23 17:22 ` Michael S. Tsirkin
2019-05-20 12:52 ` Michael S. Tsirkin [this message]
2019-05-23 2:37 ` Jason Wang
2019-05-23 2:37 ` Jason Wang
2019-05-20 12:52 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2019-05-17 4:29 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=20190520085207-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pbonzini@redhat.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 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.