linux-um archives
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "richard -rw- weinberger" <richard.weinberger@gmail.com>,
	"Toralf Förster" <toralf.foerster@gmx.de>,
	LKML <linux-kernel@vger.kernel.org>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: kernel 2.6.39 (user mode linux) crashes (2.6.38 works fine)
Date: Fri, 20 May 2011 10:35:52 -0700	[thread overview]
Message-ID: <4DD6A678.6090801@linux.intel.com> (raw)
In-Reply-To: <1305907458.1465.23.camel@gandalf.stny.rr.com>



On 05/20/2011 09:04 AM, Steven Rostedt wrote:
> On Fri, 2011-05-20 at 08:55 -0700, Darren Hart wrote:
> 
>> I suspect Toralf is hitting the WARN_ON in __unqueue_futex:
>>
>> 	if (WARN_ON(!q->lock_ptr || !spin_is_locked(q->lock_ptr)
>> 			|| plist_node_empty(&q->list)))
>>
>> Toralf, can you instrument that let us know which of conditions is
>> triggering the WARN_ON? Something like the following should be adequate
>> to get you the line number. I suspect it is plist_node_empty give the
>> git bisect results you reported.
>>
>>
>> diff --git a/kernel/futex.c b/kernel/futex.c
>> index abd5324..7f31bca 100644
>> --- a/kernel/futex.c
>> +++ b/kernel/futex.c
>> @@ -782,8 +782,11 @@ static void __unqueue_futex(struct futex_q *q)
>>  {
>>  	struct futex_hash_bucket *hb;
>>
>> -	if (WARN_ON(!q->lock_ptr || !spin_is_locked(q->lock_ptr)
>> -			|| plist_node_empty(&q->list)))
>> +	if (WARN_ON(!q->lock_ptr))
>> +		return;
>> +	if (!spin_is_locked(q->lock_ptr))
>> +		return;
>> +	if (plist_node_empty(&q->list))
>>  		return;
>>
> 

Whoops, there should have been WARN_ON's in all the if blocks... duh.

> Wait! This is where we need the WARN_ON_SMP(), do we have that patch in?

Hrm, I thought he said he was on 2.6.39-rc-something. Those patches went
in pre 2.6.39-rc1 according to gitk.

> 
> I think UML is UP, and that spin_is_locked() will always return false.
> 
> -- Steve
> 
> 

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

  parent reply	other threads:[~2011-05-20 17:35 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201105191526.31904.toralf.foerster@gmx.de>
2011-05-19 17:00 ` kernel 2.6.39 (user mode linux) crashes (2.6.38 works fine) richard -rw- weinberger
2011-05-19 17:20   ` Toralf Förster
2011-05-19 17:25     ` richard -rw- weinberger
2011-05-19 20:18   ` Toralf Förster
2011-05-19 20:43     ` Steven Rostedt
2011-05-20  7:37       ` Toralf Förster
2011-05-20  7:56         ` richard -rw- weinberger
2011-05-20  8:39           ` richard -rw- weinberger
2011-05-20  8:58             ` Toralf Förster
2011-05-20  9:02               ` richard -rw- weinberger
2011-05-20  9:19                 ` Toralf Förster
2011-05-20  8:42           ` Toralf Förster
2011-05-20 16:24             ` richard -rw- weinberger
2011-05-20 17:19               ` Steven Rostedt
2011-05-20 15:55           ` Darren Hart
2011-05-20 16:04             ` Steven Rostedt
2011-05-20 16:11               ` Steven Rostedt
2011-05-20 17:10                 ` Toralf Förster
2011-05-20 17:44                   ` Steven Rostedt
2011-05-20 17:46                   ` Steven Rostedt
2011-05-20 22:53                 ` Toralf Förster
2011-05-21  8:53                   ` Toralf Förster
2011-05-23 19:17                     ` richard -rw- weinberger
2011-05-23 19:48                       ` Toralf Förster
2011-05-21 10:12                   ` richard -rw- weinberger
2011-05-21 22:37                     ` Peter Zijlstra
2011-05-21 23:06                       ` richard -rw- weinberger
2011-05-20 17:35               ` Darren Hart [this message]
2011-05-20 17:41                 ` Steven Rostedt
     [not found] ` <201105191834.56577.toralf.foerster@gmx.de>
2011-05-20  6:44   ` richard -rw- weinberger
2011-05-20  7:43     ` Toralf Förster

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=4DD6A678.6090801@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.weinberger@gmail.com \
    --cc=rostedt@goodmis.org \
    --cc=toralf.foerster@gmx.de \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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