From: Peter Zijlstra <peterz@infradead.org>
To: xlpang@redhat.com
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Juri Lelli <juri.lelli@arm.com>, Ingo Molnar <mingo@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH v2 1/2] sched/rtmutex/deadline: Fix a PI crash for deadline tasks
Date: Fri, 8 Apr 2016 10:31:58 +0200 [thread overview]
Message-ID: <20160408083158.GV3430@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <570765F7.7070406@redhat.com>
On Fri, Apr 08, 2016 at 04:04:07PM +0800, Xunlei Pang wrote:
> On 2016/04/07 at 02:14, Peter Zijlstra wrote:
> > I would suggest doing the rt_mutex_postunlock() thing as a separate
> > patch, it has some merit outside of these changes and reduces the total
> > amount of complexity in this patch.
>
> I think the code change is necessary , as it avoids the invalid task_struct
> access issue introduced by PATCH1.
>
> Do you mean just making the code refactor using rt_mutex_postunlock()
> as a separate patch? or do I miss something?
This, a separate patch that comes before this one.
But no need to send that until you've received word from Thomas.
prev parent reply other threads:[~2016-04-08 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 12:59 [PATCH v2 1/2] sched/rtmutex/deadline: Fix a PI crash for deadline tasks Xunlei Pang
2016-04-06 12:59 ` [PATCH v2 2/2] rtmutex: Kill pi_waiters_leftmost from task_struct Xunlei Pang
2016-04-06 18:15 ` Peter Zijlstra
2016-04-06 18:14 ` [PATCH v2 1/2] sched/rtmutex/deadline: Fix a PI crash for deadline tasks Peter Zijlstra
2016-04-08 8:04 ` Xunlei Pang
2016-04-08 8:31 ` Peter Zijlstra [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160408083158.GV3430@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=xlpang@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.