netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: mst@redhat.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
	glider@google.com, dvyukov@google.com
Subject: Re: [PATCH net] vhost_net: examine pointer types during un-producing
Date: Fri, 9 Mar 2018 14:21:30 +0800	[thread overview]
Message-ID: <70ddd7d9-563b-435f-a8de-f00fc772c6d7@redhat.com> (raw)
In-Reply-To: <1520565382-4915-1-git-send-email-jasowang@redhat.com>



On 2018年03月09日 11:16, Jason Wang wrote:
> After commit 761876c857cb ("tap: XDP support"), we can actually
> queueing XDP pointers in the pointer ring, so we should examine the
> pointer type before freeing the pointer.
>
> Fixes: 761876c857cb ("tap: XDP support")

Oops, the commit is wrong, let me repost.

Thanks

> Reported-by: Michael S. Tsirkin <mst@redhat.com>
> Signed-off-by: Jason Wang <jasowang@redhat.com>
> ---
>   drivers/net/tun.c      | 3 ++-
>   drivers/vhost/net.c    | 2 +-
>   include/linux/if_tun.h | 4 ++++
>   3 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/tun.c b/drivers/net/tun.c
> index 7433bb2..28cfa64 100644
> --- a/drivers/net/tun.c
> +++ b/drivers/net/tun.c
> @@ -655,7 +655,7 @@ static struct tun_struct *tun_enable_queue(struct tun_file *tfile)
>   	return tun;
>   }
>   
> -static void tun_ptr_free(void *ptr)
> +void tun_ptr_free(void *ptr)
>   {
>   	if (!ptr)
>   		return;
> @@ -667,6 +667,7 @@ static void tun_ptr_free(void *ptr)
>   		__skb_array_destroy_skb(ptr);
>   	}
>   }
> +EXPORT_SYMBOL_GPL(tun_ptr_free);
>   
>   static void tun_queue_purge(struct tun_file *tfile)
>   {
> diff --git a/drivers/vhost/net.c b/drivers/vhost/net.c
> index 610cba2..54a138f 100644
> --- a/drivers/vhost/net.c
> +++ b/drivers/vhost/net.c
> @@ -170,7 +170,7 @@ static void vhost_net_buf_unproduce(struct vhost_net_virtqueue *nvq)
>   	if (nvq->rx_ring && !vhost_net_buf_is_empty(rxq)) {
>   		ptr_ring_unconsume(nvq->rx_ring, rxq->queue + rxq->head,
>   				   vhost_net_buf_get_size(rxq),
> -				   __skb_array_destroy_skb);
> +				   tun_ptr_free);
>   		rxq->head = rxq->tail = 0;
>   	}
>   }
> diff --git a/include/linux/if_tun.h b/include/linux/if_tun.h
> index c5b0a75..fd00170 100644
> --- a/include/linux/if_tun.h
> +++ b/include/linux/if_tun.h
> @@ -25,6 +25,7 @@ struct ptr_ring *tun_get_tx_ring(struct file *file);
>   bool tun_is_xdp_buff(void *ptr);
>   void *tun_xdp_to_ptr(void *ptr);
>   void *tun_ptr_to_xdp(void *ptr);
> +void tun_ptr_free(void *ptr);
>   #else
>   #include <linux/err.h>
>   #include <linux/errno.h>
> @@ -50,5 +51,8 @@ static inline void *tun_ptr_to_xdp(void *ptr)
>   {
>   	return NULL;
>   }
> +static inline void tun_ptr_free(void *ptr)
> +{
> +}
>   #endif /* CONFIG_TUN */
>   #endif /* __IF_TUN_H */

      parent reply	other threads:[~2018-03-09  6:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09  3:16 [PATCH net] vhost_net: examine pointer types during un-producing Jason Wang
2018-03-09  3:54 ` Michael S. Tsirkin
2018-03-09  6:21 ` Jason Wang [this message]

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=70ddd7d9-563b-435f-a8de-f00fc772c6d7@redhat.com \
    --to=jasowang@redhat.com \
    --cc=dvyukov@google.com \
    --cc=glider@google.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;
as well as URLs for NNTP newsgroup(s).