[lkml]   [2008]   [Aug]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Upcoming oops in lockdep
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 a crash (slab poison) in mark_lock is coming up
> > rapidly:
> >
> >

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

> > 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)
> 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).

 \ /
  Last update: 2008-08-25 08:57    [W:0.071 / U:4.252 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site