From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754647AbYHYGzf (ORCPT ); Mon, 25 Aug 2008 02:55:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751836AbYHYGz0 (ORCPT ); Mon, 25 Aug 2008 02:55:26 -0400 Received: from casper.infradead.org ([85.118.1.10]:56491 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751429AbYHYGzZ (ORCPT ); Mon, 25 Aug 2008 02:55:25 -0400 Subject: Re: Upcoming oops in lockdep From: Peter Zijlstra To: Arjan van de Ven Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, "Rafael J. Wysocki" In-Reply-To: <1219647117.20732.18.camel@twins> References: <20080823134955.07096e34@infradead.org> <1219647117.20732.18.camel@twins> Content-Type: text/plain Date: Mon, 25 Aug 2008 08:54:10 +0200 Message-Id: <1219647250.20732.21.camel@twins> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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).