linux-kernel - Re: [PATCH 01/12] Use mutex instead of semaphore in driver core

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: <Pine.LNX.4.64.0801081752350.25041@twin.jikos.cz>
Date:	Tue, 8 Jan 2008 17:54:02 +0100 (CET)
From:	Jiri Kosina <jikos@...os.cz>
To:	David Brownell <david-b@...bell.net>
cc:	Alan Stern <stern@...land.harvard.edu>,
	Dave Young <hidave.darkstar@...il.com>,
	Greg KH <gregkh@...e.de>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: [PATCH 01/12] Use mutex instead of semaphore in driver core

On Sat, 29 Dec 2007, David Brownell wrote:

> > There's no way to remove these, which means there's no way to prevent 
> > lockdep from issuing a warning.
> There may be no *efficient* way to do that.  If it tracked every lock 
> individually these false alarms could go away; but that would increase 
> the overhead to create and destroy such locks too.

And it would also do something completely different compared to what 
lockdep is doing now.

The point is being able to spot the potential deadlock before it actually 
happens. If you track individual instances instead of classess, you are 
out of luck with this.

-- 
Jiri Kosina
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/