mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>
Subject: Re: rb tree hrtimer lockup bug (found by perf_fuzzer)
Date: Tue, 18 Mar 2014 21:52:58 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.02.1403182149540.18573@ionos.tec.linutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.10.1403181523360.15687@vincent-weaver-1.um.maine.edu>

On Tue, 18 Mar 2014, Vince Weaver wrote:
> On Tue, 18 Mar 2014, Thomas Gleixner wrote:
> 
> > On Tue, 18 Mar 2014, Vince Weaver wrote:
> > 
> > > 
> > > The perf_fuzzer can quickly cause a machine to lockup with an hrtimer 
> > > related rb tree related oops.  I've had a hard time debugging this in any 
> > > useful manner, but I can trigger it on both core2 and haswell test systems 
> > > on 3.14-rc7.
> > > 
> > > This involves making a large number of perf_event events of all types and 
> > > then forking a lot.
> > 
> > Can you enable debugobjects please? The should give us an hint what
> > corrupts the rbtree.
> 
> I enabled debugobjects and then said Y to most of the questions brought up 
> by make oldconfig but now the system crashes at boot:

> [    3.678040] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018                                                                        
> [    3.686776] IP: [<ffffffff8106d7a8>] get_next_timer_interrupt+0x168/0x250    

The back trace is not really helpful. Is there anything before that
BUG in dmesg?

Thanks,

	tglx


  reply	other threads:[~2014-03-18 20:52 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-03 20:34 perf_fuzzer: lockup/reboot bug Vince Weaver
2014-03-04 21:32 ` Vince Weaver
2014-03-18 16:56   ` rb tree hrtimer lockup bug (found by perf_fuzzer) Vince Weaver
2014-03-18 18:21     ` Thomas Gleixner
2014-03-18 19:25       ` Vince Weaver
2014-03-18 20:52         ` Thomas Gleixner [this message]
2014-03-18 21:10           ` Vince Weaver
2014-03-18 21:45             ` Thomas Gleixner
2014-03-19 13:46               ` Vince Weaver
2014-03-19 13:58                 ` Thomas Gleixner
2014-03-19 14:42                   ` Vince Weaver
2014-03-19 15:05                     ` Thomas Gleixner
2014-03-19 17:04                       ` Vince Weaver
2014-03-20 10:47                         ` Thomas Gleixner
2014-03-20 14:47                           ` Vince Weaver
2014-03-20 15:12                             ` Thomas Gleixner
2014-03-20 21:25                               ` Vince Weaver
2014-03-21  9:02                                 ` Thomas Gleixner
2014-03-21 20:11                                   ` Vince Weaver
2014-03-22 10:24                                     ` Thomas Gleixner
2014-03-22 20:22                                       ` Thomas Gleixner
2014-03-23 15:14                                         ` Thomas Gleixner
2014-03-23 23:25                                           ` Thomas Gleixner
2014-03-25 21:06                                             ` Vince Weaver
2014-03-25 21:52                                               ` Thomas Gleixner
2014-03-26 21:33                                                 ` Vince Weaver
2014-03-26 22:00                                                   ` Thomas Gleixner
2014-03-27 13:41                                                     ` Vince Weaver
2014-03-31 11:18                                                       ` Thomas Gleixner
2014-03-31 11:46                                                         ` Ingo Molnar
2014-03-31 13:30                                                         ` Vince Weaver
2014-03-31 13:48                                                           ` Thomas Gleixner
2014-04-06  3:47                                                         ` Greg KH
2014-04-16 23:00                                                           ` Thomas Gleixner
2014-04-17  2:38                                                             ` Greg KH
2014-04-17  7:59                                                               ` Thomas Gleixner
2014-04-24 19:37                                                                 ` Greg KH

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=alpine.DEB.2.02.1403182149540.18573@ionos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=vincent.weaver@maine.edu \
    /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®