linux-kernel - Re: [patch 4/6] rtmutex: Confine deadlock logic to futex

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

Message-ID: <alpine.DEB.2.10.1405282227130.3952@nanos>
Date:	Wed, 28 May 2014 22:28:23 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Peter Zijlstra <peterz@...radead.org>
cc:	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Lai Jiangshan <laijs@...fujitsu.com>
Subject: Re: [patch 4/6] rtmutex: Confine deadlock logic to futex

On Thu, 22 May 2014, Peter Zijlstra wrote:
> On Thu, May 22, 2014 at 03:25:50AM -0000, Thomas Gleixner wrote:
> > The builtin tester is gone,, so the deadlock logic is now only
> > required for futexes.
> > 
> > Remove the extra arguments for the public functions and also for the
> > futex specific ones which get always called with deadlock detection
> > enabled.
> 
> This reminds me, the raw rt_mutex primitives have no lockdep support,
> and we've grown a few users in-tree. We should fix that.

It shouldn't be that hard. We just need to exclude the futex mess ...

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/