summaryrefslogtreecommitdiffstats
path: root/net/bluetooth/hidp/core.c
diff options
context:
space:
mode:
authorMarcel Holtmann2009-08-22 23:19:26 +0200
committerMarcel Holtmann2009-08-22 23:19:26 +0200
commit9eba32b86d17ef87131fa0bce43c614904ab5781 (patch)
treecd7e40a026475b7e4ddb8bdc944e75bc5a18c250 /net/bluetooth/hidp/core.c
parentBluetooth: Disconnect HIDRAW devices on disconnect (diff)
downloadkernel-qcow2-linux-9eba32b86d17ef87131fa0bce43c614904ab5781.tar.gz
kernel-qcow2-linux-9eba32b86d17ef87131fa0bce43c614904ab5781.tar.xz
kernel-qcow2-linux-9eba32b86d17ef87131fa0bce43c614904ab5781.zip
Bluetooth: Add extra device reference counting for connections
The device model itself has no real usable reference counting at the moment and this causes problems if parents are deleted before their children. The device model itself handles the memory details of this correctly, but the uevent order is not consistent. This causes various problems for systems like HAL or even X. So until device_put() does a proper cleanup, the device for Bluetooth connection will be protected with an extra reference counting to ensure the correct order of uevents when connections are terminated. This is not an automatic feature. Higher Bluetooth layers like HIDP or BNEP should grab this new reference to ensure that their uevents are send before the ones from the parent device. Based on a report by Brian Rogers <brian@xyzw.org> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'net/bluetooth/hidp/core.c')
0 files changed, 0 insertions, 0 deletions