All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 501] igb: segfault in rte_eth_tx_done_cleanup() when using advanced descriptors
Date: Sun, 05 Jul 2020 11:23:52 +0000	[thread overview]
Message-ID: <bug-501-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=501

            Bug ID: 501
           Summary: igb: segfault in rte_eth_tx_done_cleanup() when using
                    advanced descriptors
           Product: DPDK
           Version: 19.05
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: pawelwod@gmail.com
  Target Milestone: ---

For advanced descriptors the eth_igb_xmit_pkts() function is using one
additional TX ring descriptor entry but is not setting txe->mbuf. This gives
segfault in igb_tx_done_cleanup() as sw_ring[tx_id].mbuf is not checked before
calling  rte_pktmbuf_free_seg().

Driver code did't changed much since v19.05 so I think that the bug is still
present.

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

                 reply	other threads:[~2020-07-05 11:23 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-501-3@http.bugs.dpdk.org/ \
    --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.