From: David Miller <davem@davemloft.net>
To: jasowang@redhat.com
Cc: mst@redhat.com, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net V3 0/3] Fix various issue of vhost
Date: Wed, 12 Dec 2018 21:57:17 -0800 (PST) [thread overview]
Message-ID: <20181212.215717.702103892928039727.davem@davemloft.net> (raw)
In-Reply-To: <20181213025339.14023-1-jasowang@redhat.com>
From: Jason Wang <jasowang@redhat.com>
Date: Thu, 13 Dec 2018 10:53:36 +0800
> This series tries to fix various issues of vhost:
>
> - Patch 1 adds a missing write barrier between used idx updating and
> logging.
> - Patch 2-3 brings back the protection of device IOTLB through vq
> mutex, this fixes possible use after free in device IOTLB entries.
>
> Please consider them for -stable.
>
> Thanks
>
> Changes from V2:
> - drop dirty page fix and make it for net-next
> Changes from V1:
> - silent compiler warning for 32bit.
> - use mutex_trylock() on slowpath instead of mutex_lock() even on fast
> path.
Series applied and queued up for -stable, thanks Jason.
next prev parent reply other threads:[~2018-12-13 5:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 2:53 Jason Wang
2018-12-13 2:53 ` [PATCH net V3 1/3] vhost: make sure used idx is seen before log in vhost_add_used_n() Jason Wang
2018-12-13 2:53 ` [PATCH net V3 2/3] vhost_net: switch to use mutex_trylock() in vhost_net_busy_poll() Jason Wang
2018-12-13 2:53 ` [PATCH net V3 3/3] Revert "net: vhost: lock the vqs one by one" Jason Wang
2018-12-13 5:57 ` David Miller [this message]
2018-12-13 14:32 ` [PATCH net V3 0/3] Fix various issue of vhost Michael S. Tsirkin
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=20181212.215717.702103892928039727.davem@davemloft.net \
--to=davem@davemloft.net \
--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=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®