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

Thomas Monjalon thomas at monjalon.net
Mon Jan 25 13:39:00 CET 2021


25/01/2021 13:37, Thomas Monjalon:
> 25/01/2021 10:13, Andrew Rybchenko:
> > 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: stable at dpdk.org
> > > 
> > > Reported-by: Anatoly Burakov <anatoly.burakov at intel.com>
> > > Signed-off-by: Thomas Monjalon <thomas at monjalon.net>
> > 
> > Acked-by: Andrew Rybchenko <andrew.rybchenko at oktetlabs.ru>
> 
> Applied

Sorry please ignore this wrong message, patch not applied.
(will be considered by Ferruh)




More information about the dev mailing list