tree 813910b9600070fe35ffc594f3c0894e258ca10d
parent 7fa136531e646b0608b08a6afa85030a57a7ff33
author Jakub Kicinski <jakub.kicinski@netronome.com> 1496980570 -0700
committer David S. Miller <davem@davemloft.net> 1497027127 -0400

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>