Hi Luiz, > > what about just triggering the timer and then sending DISC for DLCI 0. I > > don't see a big benefit for this reference counting overhead. > > > > When we send the DISC, we will receive UA and thus get the required > > rfcomm_session_put() that then leads to the ACL disconnect. > > Hmm, that seems to work too and is what we are doing in case of > receiving a DM, but there is a chance that the remote stack doesn't > respond the DISC in that case we can also use the session timer to > timeout. Anyway I don't think such broken stack exist, although we do > set timeout when sending DISC to a specific DLCI, so lets leave this > for latter when he actually have a real offender which doesn't respond > with UA. > > Moving ahead, what about the timeout, 20 seconds seems too much > doesn't it? Are you fine with the places where I clear the timer? the timeout should be 2 seconds. At most 5 seconds. I still prefer if we just send DISC and then wait for the remote stack to do the right thing. If it doesn't then that stack is so broken that whatever we try to do is wrong anyway at that point. 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
