| > | but can't we just use bh_lock_sock_nested in sk_receive_skb? | > I am not sure about that one - I don't know all the functions calling | > sk_receive_skb (cscope says ppoe.c / dn_nsp_in.c use this too). | > | > In the TCP/DCCP case it is clear (due to the cloning while one is held under | > a lock), but for other contexts it might be different and cause subtle problems. | | Yup, that is why I asked, I'll investigate this further later to see | if its safe for the !INET cases. There had been an earlier attempt to do this in sk_clone, but it was abandoned since it lead to problems: http://www.mail-archive.com/dccp@xxxxxxxxxxxxxxx/msg00356.html - Gerrit - To unsubscribe from this list: send the line "unsubscribe dccp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
