Hi Johan, On Thu, Apr 12, 2012 at 11:18 AM, Johan Hedberg <johan.hedberg@xxxxxxxxx> wrote: > > Hi Mikel, > > On Thu, Apr 12, 2012, Mikel Astiz wrote: > > If I understand this correctly, this means we need some kernel > > patches. Either (a) we add the source address in sockaddr_sco so we > > can drop the bind() call (because sco_sock_connect would already > > receive both addresses), or (b) we modify sco_sock_bind such that it > > doesn't complain with EADDRINUSE. > > > > I don't have much experience with sockets but the second approach > > seems a workaround to me. > > Actually b) sounds more like a bugfix than a workaround (and a doesn't > sound like a good idea at all). Returning that error only makes sense > for server sockets but we can't know if this is a server socket or not > at the bind stage. What should probably be done is that the EADDRINUSE > isn't returned for bind() but for listen(). > > Johan I will soon send a kernel patch that follows your suggestion. Cheers, Mikel -- 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
