From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 264] ring_pmd fails to properly release used port on 17.11 branch
Date: Thu, 02 May 2019 11:23:24 +0000 [thread overview]
Message-ID: <bug-264-3@http.bugs.dpdk.org/> (raw)
Message-ID: <20190502112324.pfB13C1ikxBjlCJA30CUo4FlKeiCgfSZkeKFY5DGp40@z> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=264
Bug ID: 264
Summary: ring_pmd fails to properly release used port on 17.11
branch
Product: DPDK
Version: 17.11
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: matias.elo@nokia.com
Target Milestone: ---
During do_eth_dev_ring_create() the global eth_dev->data pointer is overwritten
with a pointer to a newly allocated memory block. When ring pmd is
uninitialized, the locally allocated data is freed but the global pointer is
newer fixed.
One symptom of this is that the used ethdev port will appear reserved even
after the ring pmd has been uninitialized.
This issue is already fixed in master branch by commit 5f19dee60 "drivers/net:
do not use private ethdev data" but this commit is missing from the LTS 17.11
branch.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-05-02 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 11:23 bugzilla [this message]
2019-05-02 11:23 ` bugzilla
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-264-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 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).