From: Andrew Morton <akpm@osdl.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [patch 2/3] rtmutex: Propagate priority settings into PI lock chains
Date: Thu, 22 Jun 2006 19:06:57 -0700 [thread overview]
Message-ID: <20060622190657.08944024.akpm@osdl.org> (raw)
In-Reply-To: <20060622082812.607857000@cruncher.tec.linutronix.de>
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.
next prev parent reply other threads:[~2006-06-23 2:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 9:08 [patch 0/3] rtmutex: Propagate priority setting into " Thomas Gleixner
2006-06-22 9:08 ` [patch 1/3] Drop tasklist lock in do_sched_setscheduler Thomas Gleixner
2006-06-23 1:48 ` Andrew Morton
2006-06-23 6:01 ` Thomas Gleixner
2006-06-24 8:07 ` Andrew Morton
2006-06-24 8:25 ` Thomas Gleixner
2006-06-22 9:08 ` [patch 2/3] rtmutex: Propagate priority settings into PI lock chains Thomas Gleixner
2006-06-22 14:20 ` Steven Rostedt
2006-06-22 18:02 ` Esben Nielsen
2006-06-23 6:27 ` Steven Rostedt
2006-06-23 2:08 ` Andrew Morton
2006-06-23 9:28 ` [PATCH -mm] bug if setscheduler is called from interrupt context Steven Rostedt
2006-06-23 2:06 ` Andrew Morton [this message]
2006-06-23 16:26 ` [patch 2/3] rtmutex: Propagate priority settings into PI lock chains Thomas Gleixner
2006-06-22 9:08 ` [patch 3/3] rtmutex: Modify rtmutex-tester to test the setscheduler propagation Thomas Gleixner
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=20060622190657.08944024.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®