From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Baranoff Subject: I40E VF nullptr Dreference: rx_mbuf_alloc_failed Date: Fri, 2 Feb 2018 11:56:08 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" To: dev@dpdk.org Return-path: Received: from mail-wr0-f182.google.com (mail-wr0-f182.google.com [209.85.128.182]) by dpdk.org (Postfix) with ESMTP id 96A663250 for ; Fri, 2 Feb 2018 17:56:10 +0100 (CET) Received: by mail-wr0-f182.google.com with SMTP id a43so15610049wrc.4 for ; Fri, 02 Feb 2018 08:56:10 -0800 (PST) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" All, I was unclear if this should be usage or dev but it seemed like a dev issue to me. 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-> adapter->eth_dev 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? Thanks, Stefan