Hi Gustavo, > Since we do not touch the parent sock in l2cap_core.c anymore we don't > need to lock it there anymore. That lock was replaced by the > l2cap_chan_lock and inside the new_connection() call for l2cap_sock.c the > parent lock is locked, so the operations that uses it can be performed > safely. > > The l2cap_chan_lock give us the needed protection to handle the incoming > connections. and what about the newly added lock_sock(parent). Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
