linux-kernel - [Patch RFC 00/37] Cleanup init_MUTEX[_LOCKED] / DECLARE

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-next>] [day] [month] [year] [list]

Message-Id: <20090726081459.455111897@linutronix.de>
Date:	Sun, 26 Jul 2009 08:17:05 -0000
From:	Thomas Gleixner <tglx@...utronix.de>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <peterz@...radead.org>
Subject: [Patch RFC 00/37]  Cleanup init_MUTEX[_LOCKED] / DECLARE_MUTEX

There are still semaphores left which are used as mutexes. Many of
them are not mutexes; they are used as completions and serialization
object at the same time. Some others are simple mutexes and nobody
bothered to clean them up.

Most of the cases have been identified in the preempt-rt patch. The
conversion to mutexes has been tested with both lockdep and mutex
debugging for quite a time. The other semaphore style users are simply
converted to semaphores and the init_MUTEX[_LOCKED] / DECLARE_MUTEX
confusion is removed.

Andrew: it would be great if we could merge the infrastructure patch
[1/n] right away. It does not change any code as it just adds
DEFINE_SEMAPHORE, semaphore_init() and semaphore_init_locked(). The
latter is marked deprecated as well as the locked init usually points
to a completion like use case. Merging it now would allow the
maintainers to queue up the cleanup patches for .32

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/