[BLOCK2MTD] WARNING: at kernel/lockdep.c:2331 lockdep_init_map()
joern at logfs.org
Sat Oct 20 05:29:50 EDT 2007
On Fri, 19 October 2007 16:04:10 -0400, Erez Zadok wrote:
> In message <20071019191433.GK26913 at lazybastard.org>, =?utf-8?B?SsO2cm4=?= Engel writes:
> > Since when roughly? 2.6.20ish? Before?
> Yeah, I guess around that time. If you want, I could go back and test each
> of my backports and see if it has the lockdep message or not.
That's ok. Just wanted to get a rough idea.
> > Side note: you don't need mtdblock:
> > # cp jffs2-empty.img /tmp/foo
> > # losetup /dev/loop0 /tmp/foo
> > # modprobe block2mtd block2mtd=/dev/loop0,128ki
> > # mount -t jffs2 mtd0 /n/lower/b0
> > It doesn't really hurt, 'tis just superfluous.
> Neat. Curious, but where does "mtd0" come from then? It's not in my /dev
> (which uses devfs on an FC6 system).
JFFS2 interprets that itself. The only reason why JFFS2 needed a block
device was to determine the minor number of the mtd underneith. So code
was added to find the correct mtd from "mtd0" or "mtd:some_name"
instead. I believe you can even disable CONFIG_BLOCK now.
And the code itself was moved to drivers/mtd/mtdsuper.c fairly recently.
Joern's library part 2:
More information about the linux-mtd