DPDK usage discussions
 help / color / mirror / Atom feed
From: Stefan Baranoff <sbaranoff@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] (no subject)
Date: Mon, 12 Feb 2018 09:25:01 -0500	[thread overview]
Message-ID: <CAHzKxpbb_j8QVmOn7hOO-S-t4zViBYGymi0Sd2=5e31MbE3d8A@mail.gmail.com> (raw)
In-Reply-To: <CAHzKxpas_MBLmQwmJbFzzQ42SRep34qaBbPbKE-xcgx7chrHRA@mail.gmail.com>


I posted this to the dev mailing list a few days ago and didn't see any
feedback so I figured I'd ask here:

I'm on DPDK 16.11.2 (CentOS packages) using the I40EVF driver and in the
case of rx_mbuf_alloc_failed there is a null pointer dereference in
drivers/net/i40e/i40e_rxtx.c line 830. The variable 'dev' is null.

Looking at it right after initializing the port/queues it appears the
source of that variable
((struct i40e_rx_queue*)rte_eth_devices[0].data->rx_queues[0])->vsi->
is null as well. I couldn't find anywhere in the code base that initialized
that variable.

What am I missing/not doing right? Where is eth_dev supposed to be
initialized and is that just missing or is vsi->adapter->eth_dev the wrong
structure to be using in the rx_mbuf_alloc_failed case?


       reply	other threads:[~2018-02-12 14:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHzKxpas_MBLmQwmJbFzzQ42SRep34qaBbPbKE-xcgx7chrHRA@mail.gmail.com>
2018-02-12 14:25 ` Stefan Baranoff [this message]
     [not found] <d61d4da786594548953efcc0503c6647@tcs.com>
     [not found] ` <2a9c8f5b288d4917806cba6ecefb6ee7@tcs.com>
     [not found]   ` <459eaf8c52084858b4bc16145336255c@tcs.com>
2020-09-21  7:54     ` satyavalli rama
2018-03-14 13:58 sharanya k
  -- strict thread matches above, loose matches on Subject: below --
2016-11-11 21:15 Yossi Barshishat
2016-05-19 12:42 dawid_jurek
2016-05-19 10:19 THEEYAGU S

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHzKxpbb_j8QVmOn7hOO-S-t4zViBYGymi0Sd2=5e31MbE3d8A@mail.gmail.com' \
    --to=sbaranoff@gmail.com \
    --cc=users@dpdk.org \


* 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).