[ BUG ] acl sysfs entry remains after connection error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi!

I've found a bug in bluetooth stack.

I use bluetooth on ARM Linux machine to simultaneously send pictures
to 2 or 3 devices.
In a L2CAP connection stage (socket L2CAP 'connect') sometimes I get a
'Connection timeout error',
which is not a disaster because I can try to connect again. However
very often I get a kernel error,
which tells me that there is a duplicate entry in sysfs (acl...).

I've checked, and indeed acl connection entries are not removed from
sysfs after a connection fail.

How can I fix this?

PS. I've got latest 2.6.26 kernel.

Regards,
Marcin Undak
--
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

[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux