Files
linux/include/net
Johan Hedberg abe84903a8 Bluetooth: Use proper nesting annotation for l2cap_chan lock
By default lockdep considers all L2CAP channels equal. This would mean
that we get warnings if a channel is locked when another one's lock is
tried to be acquired in the same thread. This kind of inter-channel
locking dependencies exist in the form of parent-child channels as well
as any channel wishing to elevate the security by requesting procedures
on the SMP channel.

To eliminate the chance for these lockdep warnings we introduce a
nesting level for each channel and use that when acquiring the channel
lock. For now there exists the earlier mentioned three identified
categories: SMP, "normal" channels and parent channels (i.e. those in
BT_LISTEN state). The nesting level is defined as atomic_t since we need
access to it before the lock is actually acquired.

Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
2014-11-13 07:49:09 +01:00
..
2014-09-18 10:54:36 +02:00
2013-12-28 17:02:46 -05:00
2014-09-26 16:14:16 -04:00
2013-11-07 19:28:58 -05:00
2014-09-30 01:02:26 -04:00
2014-06-04 22:46:38 -07:00
2013-01-27 22:46:33 -05:00
2014-06-27 15:53:35 -07:00
2014-09-05 17:40:33 -07:00
2014-01-03 20:56:48 -05:00
2014-09-30 14:00:48 -04:00
2014-10-16 14:52:35 -04:00
2014-11-09 19:50:28 +01:00
2014-08-15 13:51:40 +02:00
2014-03-24 12:45:01 -04:00
2014-06-02 11:00:41 -07:00
2014-05-22 14:57:15 -04:00
2014-10-01 21:35:51 -04:00
2014-07-07 21:14:21 -07:00