netdev - Re: [PATCH 1/2] bluetooth : use lockdep sub-classes for diffrent bluetooth protocol

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20080402.000006.218698845.davem@davemloft.net>
Date:	Wed, 02 Apr 2008 00:00:06 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	hidave.darkstar@...il.com
Cc:	davej@...emonkey.org.uk, netdev@...r.kernel.org,
	linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org,
	marcel@...tmann.org
Subject: Re: [PATCH 1/2] bluetooth : use lockdep sub-classes for diffrent
 bluetooth protocol

From: Dave Young <hidave.darkstar@...il.com>
Date: Wed, 2 Apr 2008 13:59:56 +0800

> 'rfcomm connect' will trigger lockdep warnings which is caused by
> locking diffrent kinds of bluetooth sockets at the same time.
> 
> So using sub-classes per AF_BLUETOOTH sub-type for lockdep.
> 
> Thanks for the hints from dave jones.

Applied, thanks for following up on this Dave.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html