patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Jens Freimann <jfreimann@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: maxime.coquelin@redhat.com, dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] virtio: fix buffer leak on vlan insert
Date: Fri, 5 Apr 2019 09:43:58 +0200	[thread overview]
Message-ID: <20190405074358.c5dhohtsesxiwj2m@jenstp.localdomain> (raw)
In-Reply-To: <20190405000343.24424-1-stephen@networkplumber.org>

On Thu, Apr 04, 2019 at 05:03:43PM -0700, Stephen Hemminger wrote:
>The function rte_vlan_insert may allocate a new buffer for the
>vlan header and return a different mbuf than originally passed.
>In this case, the stored mbuf in txm[] array could point to wrong
>buffer.
>
>Fixes: dd856dfcb9e7 ("virtio: use any layout on Tx")
>Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>---
> drivers/net/virtio/virtio_rxtx.c | 2 ++
> 1 file changed, 2 insertions(+)
>
>diff --git a/drivers/net/virtio/virtio_rxtx.c b/drivers/net/virtio/virtio_rxtx.c
>index e6f3706d6fe1..2ae4232c181d 100644
>--- a/drivers/net/virtio/virtio_rxtx.c
>+++ b/drivers/net/virtio/virtio_rxtx.c
>@@ -2003,6 +2003,8 @@ virtio_xmit_pkts_packed(void *tx_queue, struct rte_mbuf **tx_pkts,
> 				rte_pktmbuf_free(txm);
> 				continue;
> 			}
>+			/* vlan_insert may add a header mbuf */
>+			tx_pkts[nb_tx] = txm;
> 		}
>
> 		/* optimize ring usage */

Good catch. I think we have the same bug in virtio_xmit_pkts() and
virtio_xmit_pkts_inorder() and should fix these as well. 


Thanks!

regards,
Jens 

  reply	other threads:[~2019-04-05  7:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-05  0:03 [dpdk-stable] " Stephen Hemminger
2019-04-05  7:43 ` Jens Freimann [this message]
     [not found] ` <20190405163115.5068-1-stephen@networkplumber.org>
2019-04-08  9:21   ` [dpdk-stable] [dpdk-dev] [PATCH v2] " Jens Freimann

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=20190405074358.c5dhohtsesxiwj2m@jenstp.localdomain \
    --to=jfreimann@redhat.com \
    --cc=dev@dpdk.org \
    --cc=maxime.coquelin@redhat.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.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).