linux-kernel - Re: [Patch RFC 01/37] semaphore: Add DEFINE_SEMAPHORE, semaphore_init, semaphore_init

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 for Android: free password hash cracker in your pocket

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

Message-ID: <alpine.LFD.2.00.0907271730540.2936@localhost.localdomain>
Date:	Mon, 27 Jul 2009 17:32:26 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Christoph Hellwig <hch@...radead.org>
cc:	Daniel Walker <dwalker@...o99.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [Patch RFC 01/37] semaphore: Add DEFINE_SEMAPHORE, semaphore_init,
 semaphore_init_locked

On Mon, 27 Jul 2009, Christoph Hellwig wrote:

> On Sun, Jul 26, 2009 at 04:04:49PM -0700, Daniel Walker wrote:
> > Maybe you could introduce this _after_ you do the semaphore to
> > completion cleanup .. This init_locked is just adding a bunch of code
> > flux on top of that..
> 
> I agree.  For these 36 patches we should first check if they can
> be trivially converted to mutexes or completions and only change them
> away to the semaphore named initializers.

I have already converted some of the users to mutexes where it was
obvious. It's part of the series. 

Thanks,

	tglx
--
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/