From: Esben Nielsen <nielsen.esben@googlemail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Esben Nielsen <nielsen.esben@googlemail.com>,
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 13:26:48 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0607261307070.10713@localhost.localdomain> (raw)
In-Reply-To: <20060726085556.GA19501@elte.hu>
On Wed, 26 Jul 2006, Ingo Molnar wrote:
>
> * Ingo Molnar <mingo@elte.hu> wrote:
>
>> and i also had to do the fixes below to get it to build.
>
> then it crashed with the assert below. I'll skip this one for now. I've
> attached the patches (cleaned up for whitespaces) plus the
> build-fixpatch.
>
> Ingo
>
> Brought up 2 CPUs
> BUG at kernel/rtmutex.c:773!
> ------------[ cut here ]------------
> kernel BUG at kernel/rtmutex.c:773!
> invalid opcode: 0000 [#1]
> PREEMPT SMP
> Modules linked in:
> CPU: 0
> EIP: 0060:[<c03e407c>] Not tainted VLI
> EFLAGS: 00010246 (2.6.17-rt7 #14)
> EIP is at rt_lock_slowlock+0x21e/0x231
> eax: 00000020 ebx: c31d7000 ecx: c0477be4 edx: c31d97f0
> esi: 00000000 edi: c31d7d34 ebp: c31d7cdc esp: c31d7c70
> ds: 007b es: 007b ss: 0068 preempt: 00000001
>
>
It is a very simple bug: The waiter was made garbage by the
debug_rt_mutex_free_waiter() before it was used in the BUG_ON() line.
My UP machine boots now with CONFIG_DEBUG_RT_MUTEXEX on in -rt8. Fix
is below. Apply on top of the patches you just send me with no further
changes. I hope I don't have white space damage in this small patch!!
Esben
kernel/rtmutex.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.17-rt8/kernel/rtmutex.c
===================================================================
--- linux-2.6.17-rt8.orig/kernel/rtmutex.c
+++ linux-2.6.17-rt8/kernel/rtmutex.c
@@ -768,9 +768,9 @@ rt_lock_slowlock(struct rt_mutex *lock _
if (adjust_prio_final)
rt_mutex_adjust_prio_final(current, waiter.old_sched_lifo);
- debug_rt_mutex_free_waiter(&waiter);
BUG_ON(current->boosting_prio != MAX_PRIO);
BUG_ON(waiter.old_sched_lifo != get_sched_lifo());
+ debug_rt_mutex_free_waiter(&waiter);
}
/*
prev parent reply other threads:[~2006-07-26 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-23 1:18 Esben Nielsen
2006-07-26 8:41 ` Ingo Molnar
2006-07-26 8:54 ` Ingo Molnar
2006-07-26 8:55 ` Ingo Molnar
2006-07-26 11:24 ` Esben Nielsen
2006-07-26 12:26 ` Esben Nielsen [this message]
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=Pine.LNX.4.64.0607261307070.10713@localhost.localdomain \
--to=nielsen.esben@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®