public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Andi Kleen <ak@suse.de>
Cc: Olaf Hering <olaf@aepfle.de>,
	mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: Futex BUG in 2.6.18rc2-git7
Date: Fri, 04 Aug 2006 22:12:15 +0200	[thread overview]
Message-ID: <1154722335.5932.243.camel@localhost.localdomain> (raw)
In-Reply-To: <200608041036.47763.ak@suse.de>

On Fri, 2006-08-04 at 10:36 +0200, Andi Kleen wrote:
> On Friday 04 August 2006 10:26, Olaf Hering wrote:
> > On Fri, Aug 04, 2006 at 09:17:00AM +0200, Andi Kleen wrote:
> > > 
> > > One of my test machines (single socket core2 duo) running 2.6.18rc2-git7 over night 
> > > under moderate load threw this, followed by an endless loop of soft lockup timeouts
> > > (one exemplar appended)
> > > 
> > > I assume it is related to the new PI mutexes.
> > 
> > Maybe triggered by this, if it was from wagner.suse.de:
> 
> Yes it was that box. So it looks like the new mutex code cannot run
> the glibc test suite.

Can you retest against -rc3-current + the compat fix I sent out earlier
today (see also below) ?

Is the glibc the latest CVS version ?

	tglx


diff --git a/kernel/futex_compat.c b/kernel/futex_compat.c
index d1aab1a..c5cca3f 100644
--- a/kernel/futex_compat.c
+++ b/kernel/futex_compat.c
@@ -39,7 +39,7 @@ void compat_exit_robust_list(struct task
 {
 	struct compat_robust_list_head __user *head = curr->compat_robust_list;
 	struct robust_list __user *entry, *pending;
-	unsigned int limit = ROBUST_LIST_LIMIT, pi;
+	unsigned int limit = ROBUST_LIST_LIMIT, pi, pip;
 	compat_uptr_t uentry, upending;
 	compat_long_t futex_offset;
 
@@ -59,10 +59,10 @@ void compat_exit_robust_list(struct task
 	 * if it exists:
 	 */
 	if (fetch_robust_entry(&upending, &pending,
-			       &head->list_op_pending, &pi))
+			       &head->list_op_pending, &pip))
 		return;
 	if (upending)
-		handle_futex_death((void *)pending + futex_offset, curr, pi);
+		handle_futex_death((void *)pending + futex_offset, curr, pip);
 
 	while (compat_ptr(uentry) != &head->list) {
 		/*



  reply	other threads:[~2006-08-04 20:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-04  7:17 Futex BUG in 2.6.18rc2-git7 Andi Kleen
2006-08-04  8:26 ` Olaf Hering
2006-08-04  8:36   ` Andi Kleen
2006-08-04 20:12     ` Thomas Gleixner [this message]
2006-08-04 20:26       ` Olaf Hering

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=1154722335.5932.243.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=olaf@aepfle.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