From: Ingo Molnar <mingo@elte.hu>
To: Esben Nielsen <nielsen.esben@googlemail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch 0/3] [-rt] Fixes the timeout-bug in the rtmutex/PI-futex.
Date: Wed, 26 Jul 2006 10:54:04 +0200 [thread overview]
Message-ID: <20060726085404.GA19151@elte.hu> (raw)
In-Reply-To: <20060726084152.GA15909@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
>
> * Esben Nielsen <nielsen.esben@googlemail.com> wrote:
>
> > -- Hi,
> > I finally got around to send in the a new version of my fixes to PI.
> > The main purpose is to fix the timeout bug of the rtmutex/PI-futex.
>
> there's quite a bit of whitespace damage in your patchqueue. For
> example all the 'context' lines have an extra space at their
> beginning, which causes 'patch' to fail on every single chunk. There's
> also the occasional '8 spaces instead of a tab' buglet, probably
> introduced while writing this code.
and i also had to do the fixes below to get it to build.
Ingo
---
include/linux/rtmutex.h | 2 +-
kernel/rtmutex.c | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
Index: linux-rt.q/include/linux/rtmutex.h
===================================================================
--- linux-rt.q.orig/include/linux/rtmutex.h
+++ linux-rt.q/include/linux/rtmutex.h
@@ -116,7 +116,7 @@ extern void rt_mutex_unlock(struct rt_mu
# define INIT_RT_MUTEXES(tsk) \
.pi_waiters = PLIST_HEAD_INIT(tsk.pi_waiters, tsk.pi_lock), \
.pi_lock = RAW_SPIN_LOCK_UNLOCKED, \
- .boosting_prio = MAX_PRIO \
+ .boosting_prio = MAX_PRIO, \
INIT_RT_MUTEX_DEBUG(tsk)
#else
# define INIT_RT_MUTEXES(tsk)
Index: linux-rt.q/kernel/rtmutex.c
===================================================================
--- linux-rt.q.orig/kernel/rtmutex.c
+++ linux-rt.q/kernel/rtmutex.c
@@ -328,7 +328,7 @@ static int rt_mutex_adjust_prio_chain(ta
* Calls the rt_mutex_adjust_prio_chain() above
* whith unlocking and locking lock->wait_lock.
*/
-static void rt_mutex_adjust_prio_chain_unlock(struct rt_mutex *lock)
+static void rt_mutex_adjust_prio_chain_unlock(struct rt_mutex *lock __IP_DECL__)
{
spin_unlock(&lock->wait_lock);
get_task_struct(current);
@@ -714,7 +714,7 @@ rt_lock_slowlock(struct rt_mutex *lock _
task_blocks_on_rt_mutex(lock, &waiter, 0 __IP__);
/* Wakeup during boost ? */
else
- rt_mutex_adjust_prio_chain_unlock(lock);
+ rt_mutex_adjust_prio_chain_unlock(lock __IP__);
/*
* We got it while lock->wait_lock was unlocked ?
@@ -914,7 +914,7 @@ rt_mutex_slowlock(struct rt_mutex *lock,
ret = task_blocks_on_rt_mutex(lock, &waiter,
detect_deadlock __IP__);
else
- rt_mutex_adjust_prio_chain_unlock(lock);
+ rt_mutex_adjust_prio_chain_unlock(lock __IP__);
/*
next prev parent reply other threads:[~2006-07-26 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-23 1:18 [patch 0/3] [-rt] Fixes the timeout-bug in the rtmutex/PI-futex Esben Nielsen
2006-07-26 8:41 ` Ingo Molnar
2006-07-26 8:54 ` Ingo Molnar [this message]
2006-07-26 8:55 ` Ingo Molnar
2006-07-26 11:24 ` Esben Nielsen
2006-07-26 12:26 ` Esben Nielsen
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=20060726085404.GA19151@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=nielsen.esben@googlemail.com \
--cc=rostedt@goodmis.org \
--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