RE: Rfcomm use count

Marcel,

I've been able to get the rfcomm use count to stick above 0 using a
single-threaded app which only does RFCOMM socket calls. After killing
hciattach and all bluetooth related programs, I have this:

lsmod:
Module                  Size  Used by    Not tainted
rfcomm                 23268   2  (autoclean)
hci_uart                5656   0  (autoclean)
l2cap                  17028   1  (autoclean) [rfcomm]
bluez                  32392   0  (autoclean) [rfcomm hci_uart l2cap]

cat /proc/bluetooth/rfcomm:
sk  3A:A4:58:16:05:00 26:02:5F:16:05:00 9 4
sk  3A:A4:58:16:05:00 26:02:5F:16:05:00 9 10

This shows, I think, two sockets in the BT_CLOSED state which aren't getting
cleaned up. Kernel is 2.4.21-mh10 running on an ARM (with ARM patches, which
as far as I can tell don't touch any bluetooth code).

The test program loops, doing the following, in pseudo code:

While(1) {
        1. Connect to remote device via rfcomm
        2. send a few 100 bytes of data
        3. Attempt to receive, but the remote side closes the connection.
        4. creates a socket, binds, listens, and accepts an incomming rfcomm
connection
        5. closes the listening socket (continues to use the socket return
by accept)
        6. sends a few 100 bytes and receives ~100kB.
        7. closes the socket
}

Unfortunately the problem is not easily reproduced. It can take all day for
it to happen, with the test program being re-run many times (and stopped
with ctrl-c).

There are two modules connected via serial. On the device two copies of this
program are run, each one specifying a local bluetooth device in the bind
calls for connect and listen/accept. i.e. each program works with its own
local device and does not do anything with the other device.

Any thoughts?

-Daryl.



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idP47&alloc_id808&op=click