[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPM=9ty0B=HR-g1vLoe51LpRZH8zH1yBzTSfhJg5yXceF+afdw@mail.gmail.com>
Date: Wed, 7 Aug 2013 10:05:35 +1000
From: Dave Airlie <airlied@...il.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Maarten Lankhorst <maarten.lankhorst@...onical.com>,
Ingo Molnar <mingo@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
Alex Deucher <alexander.deucher@....com>
Subject: Re: [PATCH] mutex: fix deadlock injection
On Tue, Jul 30, 2013 at 6:41 PM, Peter Zijlstra <peterz@...radead.org> wrote:
> On Tue, Jul 30, 2013 at 10:13:41AM +0200, Maarten Lankhorst wrote:
>> The check needs to be for > 1, because ctx->acquired is already incremented.
>> This will prevent ww_mutex_lock_slow from returning -EDEADLK and not locking
>> the mutex. It caused a lot of false gpu lockups on radeon with
>> CONFIG_DEBUG_WW_MUTEX_SLOWPATH=y because a function that shouldn't be able
>> to return -EDEADLK did.
>>
>> Cc: Alex Deucher <alexander.deucher@....com>
>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@...onical.com>
Should this be merged via Ingo? or will I queue it in my -fixes?
Dave.
--
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/
Powered by blists - more mailing lists