nfp: make sure to cancel port refresh on the error path
authorJakub Kicinski <jakub.kicinski@netronome.com>
Fri, 9 Jun 2017 03:56:10 +0000 (20:56 -0700)
committerDavid S. Miller <davem@davemloft.net>
Fri, 9 Jun 2017 16:52:07 +0000 (12:52 -0400)
commitab832b8de405c640d407b4473c6875210c326255
tree813910b9600070fe35ffc594f3c0894e258ca10d
parent7fa136531e646b0608b08a6afa85030a57a7ff33
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>
drivers/net/ethernet/netronome/nfp/nfp_net_main.c