linux-kernel - Re: [patch 1/3] rtmutex: Add missing deadlock check

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

Date:	Wed, 14 May 2014 15:33:48 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Darren Hart <darren@...art.com>
cc:	Carlos ODonell <carlos@...hat.com>, laijs@...fujitsu.com,
	Dave Jones <davej@...hat.com>,
	Michael Kerrisk <mtk.manpages@...il.com>,
	Jakub Jelinek <jakub@...hat.com>,
	Roland McGrath <roland@...k.frob.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Davidlohr Bueso <davidlohr@...com>,
	Clark Williams <williams@...hat.com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
	Ingo Molnar <mingo@...nel.org>
Subject: Re: [patch 1/3] rtmutex: Add missing deadlock check

On Wed, 14 May 2014, Darren Hart wrote:
> On May 13, 2014 11:54 PM, "Thomas Gleixner" <tglx@...utronix.de> wrote:
> 
> I'll gladly accept new functional/algorithm type tests to futextest
> (performance stuff is probably going to perf instead, and Dave Miller beat

Dave Jones :)

> me to the fuzz tester with Trinity). But I think there is evidence we
> should build out the futex functional testing, and futextest seems a
> logical place for it.

Though as long as glibc is being silly we need to use the raw syscall
for it.

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/