Flush Tx skbs after link down

["Feldman, Scott" <scott.feldman@xxxxxxxxx>]

Someone most know the answer to this: What's the proper way to dispose
of Tx skbs that are owned by the h/w ("in-flight") when link was lost?
Lets say your h/w stops Tx processing when link is lost, but you've got
apps waiting for those Tx resources to be returned.  h/w isn't giving
those resources back until link is up.  Bonding doesn't like this.

We've tried walking the h/w list, and skb_orphan'ing the skbs, but that
only works if the usage count = 1.  The other solution is to tear down
and rebuild the Tx ring, but that requires a h/w reset to recover.  Yuk!

Any ideas?

-scott