On Mon, 2012-06-11 at 16:58 +0200, Eric Dumazet wrote: > On Mon, 2012-06-11 at 16:50 +0200, Sasha Levin wrote: > > > Eric, Is there something that documents at what state each of the > > callbacks in the network subsystem can be called? Like a big flow chart > > of some sorts? > > > > I'm asking because I've looked at this as well before sending this mail, > > and while the fix does look trivial, I wasn't sure whether it is really > > the correct fix, or the problem is that this callback wasn't supposed be > > called at all so something else is broken (we had such issue with > > namespaces and unshare() not long ago). > > > > I am not aware of such 'document'. > > Things change, and only *good* reference is actual source code. > > Now, take a look at sock_graft()/sock_orphan()/inet_release() ... I see. I grepped for release callbacks and the first few in the result (atm, ax_25) did check for !sk, so I guess I'll just follow what I see in other code in the future :) -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
