linux-kernel - Re: [BUG] 2.6.28.7 - ext4 : possible circular locking dependency detected

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]

Date:	Sun, 22 Feb 2009 17:18:29 -0500
From:	Theodore Tso <tytso@....edu>
To:	Giangiacomo Mariotti <gg.mariotti@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [BUG] 2.6.28.7 - ext4 : possible circular locking dependency
	detected

On Sun, Feb 22, 2009 at 06:14:57AM +0100, Giangiacomo Mariotti wrote:
> Through dmesg I got this error message :
> 
> [10484.092587] =======================================================
> [10484.092593] [ INFO: possible circular locking dependency detected ]
> [10484.092597] 2.6.28.7-my001 #1
> [10484.092600] -------------------------------------------------------
> [10484.092604] kjournald2/3695 is trying to acquire lock:
> [10484.092608]  (&meta_group_info[i]->alloc_sem){----}, at:
> [<ffffffffa039b6d9>] ext4_mb_load_buddy+0xd9/0x34a [ext4]
> [10484.092633]
> [10484.092634] but task is already holding lock:
> [10484.092638]  (&journal->j_list_lock#2){--..}, at:
> [<ffffffffa0370033>] jbd2_journal_commit_transaction+0xf06/0x117b
> [jbd2]

This is fixed in mainline after 2.6.29-rc5, in commit ba4439.  Over
this past weekend I backported the most recent set of fixes for the
2.6.28.y and 2.6.27.y series.  I've asked interested people to test
the for-stable and for-stable-2.6.27 branches of the ext4 git tree; if
I don't get any breakage reports, I'll send this set of fixes to
stable@...nel.org in the next couple of days.

Regards,

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