[lkml]   [2006]   [Jun]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch 2/3] rtmutex: Propagate priority settings into PI lock chains
On Thu, 22 Jun 2006 09:08:39 -0000
Thomas Gleixner <> wrote:

> 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 <>
> Signed-off-by: Ingo Molnar <>
> include/linux/sched.h | 2 ++
> kernel/rtmutex.c | 41 ++++++++++++++++++++++++++++++++++++-----

That file's full of lockdep droppings from a different patchset. Please
check the end result.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-06-23 04:09    [W:0.103 / U:6.792 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site