Thread (6 messages) flat view 6 messages, 4 authors, 2021-01-27

Re: [dpdk-dev] [dpdk-stable] [PATCH 1/1] ethdev: fix handling of close failure

From: Thomas Monjalon <hidden>
Date: 2021-01-25 12:39:10

25/01/2021 13:37, Thomas Monjalon:
25/01/2021 10:13, Andrew Rybchenko:
quoted
On 1/22/21 8:58 PM, Thomas Monjalon wrote:
quoted
If a failure happens when closing a port,
it was unnecessarily failing again in the function eth_err(),
because of a check against HW removal cause.
Indeed there is a big chance the port is released at this point.
Given the port is in the middle (or at the end) of a close process,
checking the error cause by accessing the port is a non-sense.
The error check is replaced by a simple return in the close function.

Bugzilla ID: 624
Fixes: 8a5a0aad5d3e ("ethdev: allow close function to return an error")
Cc: stable@dpdk.org

Reported-by: Anatoly Burakov <redacted>
Signed-off-by: Thomas Monjalon <redacted>
Acked-by: Andrew Rybchenko <redacted>
Applied
Sorry please ignore this wrong message, patch not applied.
(will be considered by Ferruh)

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help