linux-kernel - Re: [patch V3 0/7] rtmutex: Code clarification and optimization

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]

Date:	Mon, 9 Jun 2014 20:27:13 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...nel.org>,
	Lai Jiangshan <laijs@...fujitsu.com>,
	Jason Low <jason.low2@...com>, Brad Mouring <bmouring@...com>
Subject: Re: [patch V3 0/7] rtmutex: Code clarification and optimization

On Mon, 09 Jun 2014 20:28:06 -0000
Thomas Gleixner <tglx@...utronix.de> wrote:

> This is another round of clarification and optimization patches for
> the rtmutex code.
> 
> When I looked last week into the dead lock detector I spent some time
> to figure out how the various arguments and local variables are
> protected and whats the scope of the various protection algorithms, so
> I added documentation for this as well.
> 
> I also changed the last patch which avoids the requeueing in case of
> the deadlock detection only chain walk. Instead of adding tons of
> conditional to the boost/deboost code path I simply have a separate
> code path for it.

So what branch do these apply to? I tried latest Linus master and it
didn't apply.

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