From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755932Ab2B1PIY (ORCPT ); Tue, 28 Feb 2012 10:08:24 -0500 Received: from merlin.infradead.org ([205.233.59.134]:38991 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751212Ab2B1PIX convert rfc822-to-8bit (ORCPT ); Tue, 28 Feb 2012 10:08:23 -0500 Message-ID: <1330441686.11248.93.camel@twins> Subject: Re: lockdep: Warning & NULL ptr deref From: Peter Zijlstra To: Sasha Levin Cc: Ingo Molnar , Dave Jones , linux-kernel Date: Tue, 28 Feb 2012 16:08:06 +0100 In-Reply-To: References: <1330442692.3719.7.camel@lappy> <1330435782.11248.89.camel@twins> <1330438853.11248.90.camel@twins> <1330439166.11248.92.camel@twins> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2012-02-28 at 16:55 +0200, Sasha Levin wrote: > > Hmm, cute, does a kernel without lockdep explode too? If its proper > > memory corruption one would expect that. > > Looks like it only happens when lockdep is there, it also happens in > the same lockdep line of code all the time. OK, that smells.. no good idea then on how this could happen :/