Hi Marcel, On Sun, Jun 21, 2009 at 1:58 PM, Marcel Holtmann<marcel@xxxxxxxxxxxx> wrote: > Hi Luiz, > > did you actually test this change? And understand it? > Yep, this was actually one of my first attempts to fix the problem and it make no difference, but the real problem is not rfcomm_dlc reference being hold it is currently rfcomm_session reference which are not released until the remote device respond with DISC dlci 0, but in case where the remote never respond this reference will be held forever which cause the ACL to never be disconnected. There is 2 session reference being hold, one by rfcomm_dlc_link (core.c:321) which rfcomm_dlc_unlink should takes care and another one created on rfcomm_accept_connection (core.c:1837) which afaik won't go away if the remote device doesn't respond with a proper DISC to dlci 0. -- Luiz Augusto von Dentz Engenheiro de Computação -- 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
