nfp: make sure to cancel port refresh on the error path

If very last stages of netdev registering and init fail some
other netdevs and devlink ports may have been visible to user
space before we torn them back down.  In this case there is a
slight chance user may have triggered port refresh.  We need
to make sure the async work is cancelled.

We have to cancel after releasing pf->lock, so we will always
try to cancel, regardless of which part of probe has failed.

Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

diff --git a/drivers/net/ethernet/netronome/nfp/nfp_net_main.c b/drivers/net/ethernet/netronome/nfp/nfp_net_main.c
index 5f27703060c242b0b2d49f49dce0a72b49b48a50..cdd25dc5988d835f75009feb407cc38012ff59d7 100644 (file)
--- a/drivers/net/ethernet/netronome/nfp/nfp_net_main.c
+++ b/drivers/net/ethernet/netronome/nfp/nfp_net_main.c
@@ -813,6 +813,7 @@ err_ctrl_unmap:
        nfp_cpp_area_release_free(pf->data_vnic_bar);
 err_unlock:
        mutex_unlock(&pf->lock);
+       cancel_work_sync(&pf->port_refresh_work);
        return err;
 }