From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: kvm@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, glider@google.com,
davem@davemloft.net, dvyukov@google.com
Subject: Re: [PATCH net 0/3] Several fixes for vhost_net ptr_ring usage
Date: Fri, 9 Mar 2018 18:57:43 +0200 [thread overview]
Message-ID: <20180309185703-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1520578234-5565-1-git-send-email-jasowang@redhat.com>
On Fri, Mar 09, 2018 at 02:50:31PM +0800, Jason Wang wrote:
> Hi:
>
> This small series try to fix several bugs of ptr_ring usage in
> vhost_net. Please review.
>
> Thanks
ACK series, thanks Jason!
> Alexander Potapenko (1):
> vhost_net: initialize rx_ring in vhost_net_open()
>
> Jason Wang (2):
> vhost_net: keep private_data and rx_ring synced
> vhost_net: examine pointer types during un-producing
>
> drivers/net/tun.c | 3 ++-
> drivers/vhost/net.c | 8 +++++---
> include/linux/if_tun.h | 4 ++++
> 3 files changed, 11 insertions(+), 4 deletions(-)
>
> --
> 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
glider@google.com, dvyukov@google.com, davem@davemloft.net
Subject: Re: [PATCH net 0/3] Several fixes for vhost_net ptr_ring usage
Date: Fri, 9 Mar 2018 18:57:43 +0200 [thread overview]
Message-ID: <20180309185703-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1520578234-5565-1-git-send-email-jasowang@redhat.com>
On Fri, Mar 09, 2018 at 02:50:31PM +0800, Jason Wang wrote:
> Hi:
>
> This small series try to fix several bugs of ptr_ring usage in
> vhost_net. Please review.
>
> Thanks
ACK series, thanks Jason!
> Alexander Potapenko (1):
> vhost_net: initialize rx_ring in vhost_net_open()
>
> Jason Wang (2):
> vhost_net: keep private_data and rx_ring synced
> vhost_net: examine pointer types during un-producing
>
> drivers/net/tun.c | 3 ++-
> drivers/vhost/net.c | 8 +++++---
> include/linux/if_tun.h | 4 ++++
> 3 files changed, 11 insertions(+), 4 deletions(-)
>
> --
> 2.7.4
next prev parent reply other threads:[~2018-03-09 16:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 6:50 [PATCH net 0/3] Several fixes for vhost_net ptr_ring usage Jason Wang
2018-03-09 6:50 ` [PATCH net 1/3] vhost_net: initialize rx_ring in vhost_net_open() Jason Wang
2018-03-09 16:55 ` Michael S. Tsirkin
2018-03-09 16:55 ` Michael S. Tsirkin
2018-03-09 6:50 ` [PATCH net 2/3] vhost_net: keep private_data and rx_ring synced Jason Wang
2018-03-09 16:56 ` Michael S. Tsirkin
2018-03-09 16:56 ` Michael S. Tsirkin
2018-03-09 6:50 ` [PATCH net 3/3] vhost_net: examine pointer types during un-producing Jason Wang
2018-03-09 6:50 ` Jason Wang
2018-03-09 16:57 ` Michael S. Tsirkin [this message]
2018-03-09 16:57 ` [PATCH net 0/3] Several fixes for vhost_net ptr_ring usage Michael S. Tsirkin
2018-03-09 17:03 ` David Miller
2018-03-09 17:03 ` David Miller
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=20180309185703-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.