Searched hist:"1 c64834e0624c61735308138e67cc3b527f41621" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/include/net/bluetooth/ |
| H A D | rfcomm.h | diff 1c64834e0624c61735308138e67cc3b527f41621 Sun Feb 09 19:59:07 CST 2014 Peter Hurley <peter@hurleysoftware.com> Bluetooth: Release rfcomm_dev only once
No logic prevents an rfcomm_dev from being released multiple
times. For example, if the rfcomm_dev ref count is large due
to pending tx, then multiple RFCOMMRELEASEDEV ioctls may
mistakenly release the rfcomm_dev too many times. Note that
concurrent ioctls are not required to create this condition.
Introduce RFCOMM_DEV_RELEASED status bit which guarantees the
rfcomm_dev can only be released once.
NB: Since the flags are exported to userspace, introduce the status
field to track state for which userspace should not be aware.
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Tested-By: Alexander Holler <holler@ahsoftware.de>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
|
| /openbmc/linux/net/bluetooth/rfcomm/ |
| H A D | tty.c | diff 1c64834e0624c61735308138e67cc3b527f41621 Sun Feb 09 19:59:07 CST 2014 Peter Hurley <peter@hurleysoftware.com> Bluetooth: Release rfcomm_dev only once
No logic prevents an rfcomm_dev from being released multiple
times. For example, if the rfcomm_dev ref count is large due
to pending tx, then multiple RFCOMMRELEASEDEV ioctls may
mistakenly release the rfcomm_dev too many times. Note that
concurrent ioctls are not required to create this condition.
Introduce RFCOMM_DEV_RELEASED status bit which guarantees the
rfcomm_dev can only be released once.
NB: Since the flags are exported to userspace, introduce the status
field to track state for which userspace should not be aware.
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Tested-By: Alexander Holler <holler@ahsoftware.de>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
|