linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 41682] INFO: possible circular locking dependency detected .. at ext4_evict_inode
Date: Thu, 25 Aug 2011 10:28:05 GMT	[thread overview]
Message-ID: <201108251028.p7PAS5KH001824@demeter2.kernel.org> (raw)
In-Reply-To: <bug-41682-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=41682





--- Comment #4 from Witold Baryluk <baryluk@smp.if.uj.edu.pl>  2011-08-25 10:28:03 ---
I also have CONFIG_EXT4_USE_FOR_EXT23=y , hower I use it only to mount /boot
(ext3), rest of file systems are ext4. So it XT4_USE_FOR_EXT23=y is not an
issue IMHO.

Your call trace is somehow similar that it is also in ext4_evict_inode code.
However deadlock is detected in simpler condition (single CPU, with some bug
due re-aquiring lock by same task).

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2011-08-25 10:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 21:18 [Bug 41682] New: INFO: possible circular locking dependency detected .. at ext4_evict_inode bugzilla-daemon
2011-08-24 21:19 ` [Bug 41682] " bugzilla-daemon
2011-08-24 21:22 ` bugzilla-daemon
2011-08-25  6:49 ` bugzilla-daemon
2011-08-25 10:28 ` bugzilla-daemon [this message]
2011-08-25 10:32 ` bugzilla-daemon
2011-08-25 10:34 ` bugzilla-daemon
2011-08-29  2:59 ` bugzilla-daemon
2011-08-30 10:51 ` bugzilla-daemon
2011-08-31 16:13 ` bugzilla-daemon
2011-09-02 11:27 ` bugzilla-daemon
2011-09-02 13:09 ` bugzilla-daemon
2011-09-06  5:56 ` bugzilla-daemon
2012-02-07 12:41 ` bugzilla-daemon
2012-08-30 10:46 ` bugzilla-daemon

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=201108251028.p7PAS5KH001824@demeter2.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).