From: Theodore Tso <tytso@mit.edu>
To: Giangiacomo Mariotti <gg.mariotti@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.28.7 - ext4 : possible circular locking dependency detected
Date: Sun, 22 Feb 2009 17:18:29 -0500 [thread overview]
Message-ID: <20090222221828.GH17066@mit.edu> (raw)
In-Reply-To: <12bfabe40902212114h271b3728tac48b8283d33c20b@mail.gmail.com>
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@kernel.org in the next couple of days.
Regards,
- Ted
prev parent reply other threads:[~2009-02-22 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-22 5:14 [BUG] 2.6.28.7 - ext4 : possible circular locking dependency detected Giangiacomo Mariotti
2009-02-22 22:18 ` Theodore Tso [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090222221828.GH17066@mit.edu \
--to=tytso@mit.edu \
--cc=gg.mariotti@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.