* [dpdk-dev] [Bug 264] ring_pmd fails to properly release used port on 17.11 branch
@ 2019-05-02 11:23 bugzilla
2019-05-02 11:23 ` bugzilla
0 siblings, 1 reply; 2+ messages in thread
From: bugzilla @ 2019-05-02 11:23 UTC (permalink / raw)
To: dev
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* [dpdk-dev] [Bug 264] ring_pmd fails to properly release used port on 17.11 branch
2019-05-02 11:23 [dpdk-dev] [Bug 264] ring_pmd fails to properly release used port on 17.11 branch bugzilla
@ 2019-05-02 11:23 ` bugzilla
0 siblings, 0 replies; 2+ messages in thread
From: bugzilla @ 2019-05-02 11:23 UTC (permalink / raw)
To: dev
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-05-02 11:23 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-05-02 11:23 [dpdk-dev] [Bug 264] ring_pmd fails to properly release used port on 17.11 branch bugzilla
2019-05-02 11:23 ` bugzilla
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).