Messages in this thread | | | Subject | Re: [patch 2/3] rtmutex: Propagate priority settings into PI lock chains | From | Thomas Gleixner <> | Date | Fri, 23 Jun 2006 18:26:57 +0200 |
| |
On Thu, 2006-06-22 at 19:06 -0700, Andrew Morton wrote: > On Thu, 22 Jun 2006 09:08:39 -0000 > Thomas Gleixner <tglx@linutronix.de> 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 <tglx@linutronix.de> > > Signed-off-by: Ingo Molnar <mingo@elte.hu> > > > > 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.
Will do in a minute
tglx
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |