linux-kernel - Re: lockdep with reiserfs

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20091230010519.GD5258@nowhere>
Date:	Wed, 30 Dec 2009 02:05:22 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: lockdep with reiserfs

On Wed, Dec 23, 2009 at 04:30:23PM -0800, Yinghai Lu wrote:
> 2009/12/22 Ingo Molnar <mingo@...e.hu>:
> >
> > * Yinghai Lu <yinghai@...nel.org> wrote:
> >
> >> x:~ # mount /dev/sda2 /xx
> >>
> >> [  277.586941] =======================================================
> >> [  277.594680] [ INFO: possible circular locking dependency detected ]
> >> [  277.601299] 2.6.33-rc1-tip-yh-00304-g97a015d-dirty #1007
> >> [  277.605492] -------------------------------------------------------
> >> [  277.622611] mount/19427 is trying to acquire lock:
> >> [  277.627353]  (&journal->j_mutex){+.+...}, at: [<ffffffff811c6d40>]
> >> do_journal_begin_r+0x9f/0x308
> >
> > Frederic has posted the patch below to lkml - does it do the trick for you?
> >
> with that patch, the problem still happen...
> 
> how to duplicate it:
> 1. boot sles 11 to user mode
> 2. hard reset the system
> 3. boot from network, current kernel with ramdisk as /
> 4. mount the root fs of sles11, will get this warning.
> 
> YH


Thanks for your report.

I have troubles to understand how that can happen since
the lock doesn't seem to be recursively acquired there.

Anyway, looking at the path, it seems to happen when unlinks
and truncate were unfinished (case of a hard reset) and become
resumed at mount time.

I'm trying to reproduce it, thanks!

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