On 1/25/2021 9:13 AM, Andrew Rybchenko wrote:
On 1/22/21 8:58 PM, Thomas Monjalon wrote:
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: sta...@dpdk.org
Reported-by: Anatoly Burakov <anatoly.bura...@intel.com>
Signed-off-by: Thomas Monjalon <tho...@monjalon.net>
Acked-by: Andrew Rybchenko <andrew.rybche...@oktetlabs.ru>
Applied to dpdk-next-net/main, thanks.
