From: Peter Zijlstra <peterz@infradead.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: peterz@infradeads.org, mingo@elte.hu,
linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: Upcoming oops in lockdep
Date: Mon, 25 Aug 2008 08:51:57 +0200 [thread overview]
Message-ID: <1219647117.20732.18.camel@twins> (raw)
In-Reply-To: <20080823134955.07096e34@infradead.org>
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).
next prev parent reply other threads:[~2008-08-25 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-23 20:49 Upcoming oops in lockdep Arjan van de Ven
2008-08-25 6:51 ` Peter Zijlstra [this message]
2008-08-25 6:54 ` Peter Zijlstra
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=1219647117.20732.18.camel@twins \
--to=peterz@infradead.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradeads.org \
--cc=rjw@sisk.pl \
/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