[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140515080753.GB30445@twins.programming.kicks-ass.net>
Date: Thu, 15 May 2014 10:07:53 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Carlos O'Donell <carlos@...hat.com>
Cc: Darren Hart <dvhart@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
Dave Jones <davej@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Darren Hart <darren@...art.com>,
Davidlohr Bueso <davidlohr@...com>,
Ingo Molnar <mingo@...nel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Clark Williams <williams@...hat.com>,
Paul McKenney <paulmck@...ux.vnet.ibm.com>,
Lai Jiangshan <laijs@...fujitsu.com>,
Roland McGrath <roland@...k.frob.com>,
Jakub Jelinek <jakub@...hat.com>,
Michael Kerrisk <mtk.manpages@...il.com>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Subject: Re: [patch 0/3] futex/rtmutex: Fix issues exposed by trinity
On Wed, May 14, 2014 at 05:17:35PM -0400, Carlos O'Donell wrote:
> > No, its perfectly fine to have a lock sequence abort with -EDEADLK.
> > Userspace should release its locks and re-attempt.
>
> I agree. If I can prove that it's actually a deadlock, and
> that unlock/relock will work to fix it, then we can arrange for glibc
> to return EDEADLK.
The only reason the kernel would return EDEADLK is because its walked
the lock graph and determined its well, a deadlock.
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists