[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1901301259520.5537@nanos.tec.linutronix.de>
Date: Wed, 30 Jan 2019 13:01:02 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Peter Zijlstra <peterz@...radead.org>
cc: Heiko Carstens <heiko.carstens@...ibm.com>,
Ingo Molnar <mingo@...nel.org>,
Martin Schwidefsky <schwidefsky@...ibm.com>,
LKML <linux-kernel@...r.kernel.org>, linux-s390@...r.kernel.org,
Stefan Liebler <stli@...ux.ibm.com>,
Sebastian Sewior <bigeasy@...utronix.de>
Subject: Re: [PATCH] futex: Handle early deadlock return correctly
On Tue, 29 Jan 2019, Thomas Gleixner wrote:
> int __rt_mutex_start_proxy_lock(struct rt_mutex *lock,
> struct rt_mutex_waiter *waiter,
> struct task_struct *task)
> {
> int ret;
>
> + lockdep_asssert_held(&lock->wait_lock);
I'm a moron. I fixed that on the test box and wrote the changelog on the
laptop. Syncing the two together was too much for my futex wreckaged brain
...
Powered by blists - more mailing lists