From: Eric Paris <eparis@redhat.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: Miles Lane <miles.lane@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Alan Stern <stern@rowland.harvard.edu>, Greg KH <greg@kroah.com>,
Matthew Dharm <mdharm-usb@one-eyed-alien.net>,
David Brownell <dbrownell@users.sourceforge.net>
Subject: Re: 2.6.31-rc2 -- INFO: inconsistent lock state -- inconsistent {IN-RECLAIM_FS-W} -> {RECLAIM_FS-ON-W} usage.
Date: Wed, 08 Jul 2009 10:24:27 -0400 [thread overview]
Message-ID: <1247063067.2830.2.camel@dhcp235-23.rdu.redhat.com> (raw)
In-Reply-To: <adafxd7x25h.fsf@cisco.com>
On Tue, 2009-07-07 at 20:51 -0700, Roland Dreier wrote:
> [ adding Eric Paris cc as this looks to be an inotify issue ]
>
> > [ 6627.976224] =================================
> > [ 6627.976237] [ INFO: inconsistent lock state ]
> > [ 6627.976247] 2.6.31-rc2 #16
> > [ 6627.976254] ---------------------------------
> > [ 6627.976263] inconsistent {IN-RECLAIM_FS-W} -> {RECLAIM_FS-ON-W} usage.
> > [ 6627.976276] khubd/217 [HC0[0]:SC0[0]:HE1:SE1] takes:
> > [ 6627.976285] (iprune_mutex){+.+.?.}, at: [<c10ba899>]
> > invalidate_inodes+0x20/0xe3
> > [ 6627.976315] {IN-RECLAIM_FS-W} state was registered at:
> > [ 6627.976324] [<c10536ab>] __lock_acquire+0x2c9/0xac4
> > [ 6627.976343] [<c1053f45>] lock_acquire+0x9f/0xc2
> > [ 6627.976358] [<c1308872>] __mutex_lock_common+0x2d/0x323
> > [ 6627.976376] [<c1308c00>] mutex_lock_nested+0x2e/0x36
> > [ 6627.976392] [<c10ba6ff>] shrink_icache_memory+0x38/0x1b2
> > [ 6627.976407] [<c108bfb6>] shrink_slab+0xe2/0x13c
> > [ 6627.976424] [<c108c3e1>] kswapd+0x3d1/0x55d
> > [ 6627.976439] [<c10449b5>] kthread+0x66/0x6b
> > [ 6627.976454] [<c1003fdf>] kernel_thread_helper+0x7/0x10
> > [ 6627.976472] [<ffffffff>] 0xffffffff
It could be a real bug. Reminds me a lot of
http://lkml.org/lkml/2009/4/29/782 but not the same thing since I've
removed all allocation under *notify locks. I'll try to put something
together this afternoon....
-Eric
prev parent reply other threads:[~2009-07-08 14:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 4:22 Miles Lane
2009-07-08 3:51 ` Roland Dreier
2009-07-08 14:24 ` Eric Paris [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=1247063067.2830.2.camel@dhcp235-23.rdu.redhat.com \
--to=eparis@redhat.com \
--cc=dbrownell@users.sourceforge.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=miles.lane@gmail.com \
--cc=rdreier@cisco.com \
--cc=stern@rowland.harvard.edu \
/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®