Closed GoogleCodeExporter closed 8 years ago
the idea of rfcomm_close_connection has been to let rfcomm know, that the
client connection is gone. So, I'll just have to fix the use after free
(similarly, l2cap_close_connection is called)
Original comment by matthias.ringwald@gmail.com
on 9 Aug 2014 at 11:35
i've set the connection field to NULL in both l2cap_close_connection and
rfcomm_close_connection in r2716. Now, all other clients would get the close
event, that's not elegant. Will think about it a bit more.
Original comment by matthias.ringwald@gmail.com
on 9 Aug 2014 at 11:44
Thinking is over: :)
l2cap/rfcomm shouldn't know anything about "daemon connections". I'll remove
the x_close_connections into daemon.c and keep a list of open channels and
services linked to the connection there. That's a bit of extra memory in the
daemon, but leads to cleaner code in l2cap/rfcomm. (then, I'll rename
connection into context, as it is common with many APIs)
Original comment by matthias.ringwald@gmail.com
on 9 Aug 2014 at 12:30
Thanks, sounds good.
Original comment by kob...@mce-sys.com
on 21 Aug 2014 at 1:51
Original comment by matthias.ringwald@gmail.com
on 5 Sep 2014 at 7:16
Original issue reported on code.google.com by
kob...@mce-sys.com
on 16 Jun 2014 at 12:07