* Upcoming oops in lockdep
@ 2008-08-23 20:49 Arjan van de Ven
2008-08-25 6:51 ` Peter Zijlstra
0 siblings, 1 reply; 3+ messages in thread
From: Arjan van de Ven @ 2008-08-23 20:49 UTC (permalink / raw)
To: peterz; +Cc: mingo, linux-kernel, Rafael J. Wysocki
in kerneloops.org a crash (slab poison) in mark_lock is coming up
rapidly:
http://www.kerneloops.org/searchweek.php?search=mark_lock
and despite a few earlier hits on the same function it seems to be
something introduced in 2.6.27-rc... (the older ones aren't slab poison)
--
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Upcoming oops in lockdep
2008-08-23 20:49 Upcoming oops in lockdep Arjan van de Ven
@ 2008-08-25 6:51 ` Peter Zijlstra
2008-08-25 6:54 ` Peter Zijlstra
0 siblings, 1 reply; 3+ messages in thread
From: Peter Zijlstra @ 2008-08-25 6:51 UTC (permalink / raw)
To: Arjan van de Ven; +Cc: peterz, mingo, linux-kernel, Rafael J. Wysocki
On Sat, 2008-08-23 at 13:49 -0700, Arjan van de Ven wrote:
> in kerneloops.org a crash (slab poison) in mark_lock is coming up
> rapidly:
>
> http://www.kerneloops.org/searchweek.php?search=mark_lock
>
> and despite a few earlier hits on the same function it seems to be
> something introduced in 2.6.27-rc... (the older ones aren't slab poison)
infradeads.org hehe
can this crash be reproduced without lockdep? Normally when I see
crashes like this its crashing because the lock itself is stomped on
(use after free, for example), and lockdep happens to be the one to
touch it first (the lockdep state is by far the largest bit of the
spinlock data too).
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Upcoming oops in lockdep
2008-08-25 6:51 ` Peter Zijlstra
@ 2008-08-25 6:54 ` Peter Zijlstra
0 siblings, 0 replies; 3+ messages in thread
From: Peter Zijlstra @ 2008-08-25 6:54 UTC (permalink / raw)
To: Arjan van de Ven; +Cc: mingo, linux-kernel, Rafael J. Wysocki
On Mon, 2008-08-25 at 08:51 +0200, Peter Zijlstra wrote:
> On Sat, 2008-08-23 at 13:49 -0700, Arjan van de Ven wrote:
> > in kerneloops.org a crash (slab poison) in mark_lock is coming up
> > rapidly:
> >
> > http://www.kerneloops.org/searchweek.php?search=mark_lock
Also, would be marvelous if you can at least put one of these bug
reports in the email, saves me from having to grope for a web browser
thingy.
> > and despite a few earlier hits on the same function it seems to be
> > something introduced in 2.6.27-rc... (the older ones aren't slab poison)
>
> infradeads.org hehe
>
> can this crash be reproduced without lockdep? Normally when I see
> crashes like this its crashing because the lock itself is stomped on
> (use after free, for example), and lockdep happens to be the one to
> touch it first (the lockdep state is by far the largest bit of the
> spinlock data too).
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-08-25 6:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-08-23 20:49 Upcoming oops in lockdep Arjan van de Ven
2008-08-25 6:51 ` Peter Zijlstra
2008-08-25 6:54 ` Peter Zijlstra
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox