[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <55270386.4060304@hp.com>
Date: Thu, 09 Apr 2015 16:56:06 -0600
From: Thavatchai Makphaibulchoke <thavatchai.makpahibulchoke@...com>
To: Thomas Gleixner <tglx@...utronix.de>
CC: Steven Rostedt <rostedt@...dmis.org>,
Thavatchai Makphaibulchoke <tmac@...com>,
linux-kernel@...r.kernel.org, mingo@...hat.com,
linux-rt-users@...r.kernel.org, umgwanakikbuti@...il.com,
Peter Zijlstra <peterz@...radead.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Subject: Re: [PATCH v2 1/2] rtmutex Real-Time Linux: Fixing kernel BUG at
kernel/locking/rtmutex.c:997!
On 04/08/2015 02:50 AM, Thomas Gleixner wrote:
>
> Don't even try to get this working. Taking the lock in idle/interrupt
> context is just plain wrong.
>
Thanks for the comments.
Could you please confirm you meant rt_mutex as it can go to sleep.
> The proper solution is to get rid of the locking requirement and that
> needs some thought on the timer wheel code.
>
Yes, I agree fixing the problem in the timer code is the proper
solution. BTW, once the code is fixed, I think we should add
WARN_ON(in_irq()); to the function spin_do_trylock() to prevent any
invalid future usage.
Thanks,
Mak.
> 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/
Powered by blists - more mailing lists