]> nv-tegra.nvidia Code Review - linux-2.6.git/commit
[PATCH] rtmutex: Propagate priority settings into PI lock chains
authorThomas Gleixner <tglx@linutronix.de>
Tue, 27 Jun 2006 09:55:02 +0000 (02:55 -0700)
committerLinus Torvalds <torvalds@g5.osdl.org>
Wed, 28 Jun 2006 00:32:48 +0000 (17:32 -0700)
commit95e02ca9bb5324360e7dea1ea1c563036d84a5e6
tree0336dd808abe113b42f53a8f700d50ea6ba674ff
parent0bafd214e4ba55dc1fb81a3031d0249292f1bc05
[PATCH] rtmutex: Propagate priority settings into PI lock chains

When the priority of a task, which is blocked on a lock, changes we must
propagate this change into the PI lock chain.  Therefor the chain walk code
is changed to get rid of the references to current to avoid false positives
in the deadlock detector, as setscheduler might be called by a task which
holds the lock on which the task whose priority is changed is blocked.

Also add some comments about the get/put_task_struct usage to avoid
confusion.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
include/linux/sched.h
kernel/rtmutex.c
kernel/sched.c