linux-kernel - Re: Upcoming oops in lockdep

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1219647250.20732.21.camel@twins>
Date:	Mon, 25 Aug 2008 08:54:10 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	mingo@...e.hu, linux-kernel@...r.kernel.org,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: 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 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).

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/