Re: [patch 2/3] rtmutex: Propagate priority settings into PI lock chains

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 22 Jun 2006 09:08:39 -0000
Thomas Gleixner <[email protected]> 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 <[email protected]>
> Signed-off-by: Ingo Molnar <[email protected]>
> 
>  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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux