linux-kernel - Re: [BLOCK2MTD] WARNING: at kernel/lockdep.c:2331 lockdep_init

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <200710192037.l9JKbSsh018946@agora.fsl.cs.sunysb.edu>
Date:	Fri, 19 Oct 2007 16:37:28 -0400
From:	Erez Zadok <ezk@...sunysb.edu>
To:	Jörn Engel <joern@...fs.org>
Cc:	Erez Zadok <ezk@...sunysb.edu>, dwmw2@...radead.org,
	linux-kernel@...r.kernel.org, linux-mtd@...ts.infradead.org
Subject: Re: [BLOCK2MTD] WARNING: at kernel/lockdep.c:2331 lockdep_init_map() 

In message <20071019191433.GK26913@...ybastard.org>, =?utf-8?B?SsO2cm4=?= Engel writes:
> On Fri, 19 October 2007 13:53:40 -0400, Erez Zadok wrote:
> >
> > I've been having this problem for some time with mtd, which I use to mount
> > jffs2 images (for unionfs testing).  I've seen it in several recent major
> > kernels, including 2.6.24.  Here's the sequence of ops I perform:
> 
> Since when roughly?  2.6.20ish?  Before?

I was able to verify that the same lockdep warning comes up in every major
kernel all the way back to 2.6.18.  Of course the line number in lockdep.c
that causes the warning is slightly different from kernel to kernel, but the
stack trace is the same.

Hope this helps.

Erez.
-
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/