[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 4 Apr 2017 09:13:02 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
RT-users <linux-rt-users@...r.kernel.org>,
Sebastian Siewior <bigeasy@...utronix.de>,
Julia Cartwright <julia@...com>, Wargreen <wargreen@...ib.org>,
rt-stable@...r.kernel.org
Subject: Re: [patch RT 1/4] rtmutex: Make lock_killable work
On Mon, Apr 03, 2017 at 11:21:26AM -0400, Steven Rostedt wrote:
> On Sat, 01 Apr 2017 12:50:59 +0200
> Thomas Gleixner <tglx@...utronix.de> wrote:
>
> > Locking an rt mutex killable does not work because signal handling is
> > restricted to TASK_INTERRUPTIBLE.
> >
> > Use signal_pending_state() unconditionaly.
>
> Does this mean rt mutex killable is not INTERRUPTIBLE? because the
> change log seems to just assume that.
> > - if (unlikely(state == TASK_INTERRUPTIBLE)) {
#define TASK_KILLABLE (TASK_WAKEKILL | TASK_UNINTERRUPTIBLE)
I don't think we need to consider people who don't know where to find
the TASK_state definitions.
Powered by blists - more mailing lists