All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Rusty Russell <rusty@rustcorp.com.au>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] cpumask: remove cpumask allocation from idle_balance
Date: Fri, 20 Mar 2009 18:48:01 +0100	[thread overview]
Message-ID: <20090320174801.GA7341@elte.hu> (raw)
In-Reply-To: <20090319162942.GA21672@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> 
> * Ingo Molnar <mingo@elte.hu> wrote:
> 
> > > This time for sure,
> > 
> > not so sure:
> > 
> > [    4.303068] =============================================================================
> > [    4.303332] BUG idr_layer_cache: Redzone overwritten
> > [    4.303332] -----------------------------------------------------------------------------
> > [    4.303332] 
> > [    4.303332] INFO: 0xffff88003f838958-0xffff88003f83895f. First byte 0xa1 instead of 0xbb
> > [    4.303332] INFO: Allocated in 0xffff88003f9b94b0 age=4294878587 cpu=2 pid=0
> > [    4.303332] INFO: Freed in 0xffff88003f8389f0 age=18446744073709463001 cpu=4294967295 pid=0
> > [    4.303332] INFO: Slab 0xffffe200015d5340 objects=13 used=10 fp=0xffff88003f838738 flags=0x40000000000020c3
> > [    4.303332] INFO: Object 0xffff88003f838738 @offset=1848 fp=0x(null)
> 
> hm, i'm seeing this even with the cpus4096 bits removed.
> 
> It _seems_ to trigger when i add these two commits:
> 
>   71ff49d: x86: with the last user gone, remove set_pte_present
>   b40c757: x86/32: no need to use set_pte_present in set_pte_vaddr
> 
> but i'm not completely sure it's related, i tried a bisection and it 
> showed heisenbug properties.
> 
> Might have come from upstream, that saw some IDR changes recently.

This one has not retriggered - but when i could reproduce it it 
would trigger about 50% of the time.

So there's no real correlation to the cpumask changes (sorry 
Rusty!). I'd say it's upstream originated, but it's hard to tell 
without a reliable reproducer.

	Ingo

  parent reply	other threads:[~2009-03-20 17:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18 21:33 [BUG] circular lock dependency in tip Steven Rostedt
2009-03-18 21:51 ` Steven Rostedt
2009-03-19  0:59   ` Rusty Russell
2009-03-19  2:27     ` Steven Rostedt
2009-03-19  4:52       ` [PATCH] cpumask: remove cpumask allocation from idle_balance Rusty Russell
2009-03-19 12:40         ` Rusty Russell
2009-03-19 13:24           ` Ingo Molnar
2009-03-19 13:25             ` Ingo Molnar
2009-03-19 16:29             ` Ingo Molnar
2009-03-19 16:55               ` Jeremy Fitzhardinge
2009-03-19 17:01                 ` Ingo Molnar
2009-03-20 17:48               ` Ingo Molnar [this message]
2009-03-19  7:36 ` [tip:cpus4096] " Rusty Russell
2009-03-19  8:30   ` [crash] " Ingo Molnar
2009-03-19 13:03 ` [tip:cpus4096] cpumask: remove cpumask allocation from idle_balance, fix Rusty Russell

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=20090320174801.GA7341@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=rusty@rustcorp.com.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.