All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 57] ixgbe crash on detach when no VF is created
Date: Wed, 30 May 2018 17:25:28 +0000	[thread overview]
Message-ID: <bug-57-3@http.dpdk.org/tracker/> (raw)

https://dpdk.org/tracker/show_bug.cgi?id=57

            Bug ID: 57
           Summary: ixgbe crash on detach when no VF is created
           Product: DPDK
           Version: 18.05
          Hardware: All
                OS: Linux
            Status: CONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: ferruh.yigit@intel.com
  Target Milestone: ---

Issue reported by Anatoly Burakov <anatoly.burakov@intel.com>


Steps to reproduce (with ixgbe port):
./testpmd -- -i
> port stop all
> port close all
> port detach 0


The reason of the crash is:
(*vfinfo) is a null pointer at that point, -> dereferences it. 


The issue is introduced in:
commit cf80ba6e2038a54b6c5ba62ce4200234f5aa3880
Author: Declan Doherty <declan.doherty@intel.com>
Date:   Thu Apr 26 11:41:05 2018 +0100

    net/ixgbe: add support for representor ports

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2018-05-30 17:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-57-3@http.dpdk.org/tracker/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.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.