From: Paul Bolle <pebolle@tiscali.nl>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: Linux PM mailing list <linux-pm@lists.linux-foundation.org>,
linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [BUG] INFO: inconsistent lock state
Date: Mon, 26 Sep 2011 11:34:38 +0200 [thread overview]
Message-ID: <1317029678.3536.29.camel@x61.thuisdomein> (raw)
In-Reply-To: <1317026416.3536.23.camel@x61.thuisdomein>
On Mon, 2011-09-26 at 10:40 +0200, Paul Bolle wrote:
> Something very similar happened to be in the logs of a machine running
> v3.0.4 too. It happened a few days ago (but I missed it initially). I
> have no idea what triggered this:
>
> kernel: [ 3501.569697]
> kernel: [ 3501.569699] =================================
> kernel: [ 3501.569703] [ INFO: inconsistent lock state ]
> kernel: [ 3501.569706] 3.0.4-local0.fc14.x86_64 #1
> kernel: [ 3501.569708] ---------------------------------
> kernel: [ 3501.569711] inconsistent {RECLAIM_FS-ON-W} -> {IN-RECLAIM_FS-W} usage.
> kernel: [ 3501.569714] kswapd0/25 [HC0[0]:SC0[0]:HE1:SE1] takes:
> kernel: [ 3501.569717] (&sb->s_type->i_mutex_key#13){+.+.?.}, at: [<ffffffff811b08eb>] ext4_evict_inode+0x41/0x255
> [...]
A bit of background: ext4_evict_inode+0x41 should be the call to
mutex_lock() in ext4_evict_inode():
(gdb) disass /m ext4_evict_inode+48,+17
Dump of assembler code from 0xffffffff811b08da to 0xffffffff811b08eb:
193 mutex_lock(&inode->i_mutex);
0xffffffff811b08da <ext4_evict_inode+48>: lea 0x80(%rbx),%r12
0xffffffff811b08e1 <ext4_evict_inode+55>: xor %esi,%esi
0xffffffff811b08e3 <ext4_evict_inode+57>: mov %r12,%rdi
0xffffffff811b08e6 <ext4_evict_inode+60>: callq 0xffffffff814edf03 <mutex_lock_nested>
End of assembler dump.
That call to mutex_lock() and the following call to mutex_unlock() was
added by the backport of commit 2581fdc8 ("ext4: call ext4_ioend_wait
and ext4_flush_completed_IO in ext4_evict_inode") to v3.0 in the v3.0.4
patch.
Paul Bolle
next prev parent reply other threads:[~2011-09-26 9:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 9:16 Srivatsa S. Bhat
2011-09-26 8:40 ` Paul Bolle
2011-09-26 9:34 ` Paul Bolle [this message]
2011-09-26 9:51 ` Srivatsa S. Bhat
-- strict thread matches above, loose matches on Subject: below --
2009-01-06 2:34 Li Zefan
2009-01-06 10:18 ` Zdenek Kabelac
2009-01-06 10:25 ` Li Zefan
2009-01-06 10:47 ` Zdenek Kabelac
2009-01-06 12:38 ` Zdenek Kabelac
2009-01-07 12:16 ` Herbert Xu
2009-01-06 13:53 ` Zdenek Kabelac
2009-01-07 12:13 ` Herbert Xu
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=1317029678.3536.29.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
/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
all inboxes | Powered by JetHome®