Hi, On 13 February 2014 15:13, Andrzej Kaczmarek <andrzej.kaczmarek@xxxxxxxxx> wrote: > When binding RFCOMM socket with non-zero channel we're checking if > there is already any other socket which has the same channel number > assigned and then fail. This check does not consider situation where > we have another socket connected to remote device on given channel > number in which case we still should be able to bind local socket. > > This patch changes __rfcomm_get_sock_by_addr() to return only sockets > in either BT_BOUND or BT_LISTEN states, also name is updated to better > describe what this function does now. > > Signed-off-by: Andrzej Kaczmarek <andrzej.kaczmarek@xxxxxxxxx> ping...? BR, Andrzej -- 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