David S. Miller wrote:
> > which is always going to be in user context. its a bit subtle but
> > there is no path to unlink_clip_vcc() that isnt in user context.
> Are you really totally sure that no interrupt path can release
> a VCC?
That should be the case at least for any VCC on a real interface[*].
Some ATM cards have ->close() methods that can take a while so connection
teardown has to happen with some sort of sleepable context. So if there
are cases where an interrupt causes the VCC to die they would need to be
[*] some protocols use psuedo-interfaces for their control connections - in
theory I guess they could be different but I don't believe there are
any cases where they are. They wouldn't affect this issue anyways though.