From: Valdis.Kletnieks@vt.edu
To: Jan Kara <jack@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: mmotm 2010-11-09 - lockdep splat in ext4/quota code
Date: Thu, 25 Nov 2010 00:35:50 -0500 [thread overview]
Message-ID: <28481.1290663350@localhost> (raw)
In-Reply-To: Your message of "Sat, 13 Nov 2010 00:33:43 +0100." <20101112233343.GA12153@quack.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
On Sat, 13 Nov 2010 00:33:43 +0100, Jan Kara said:
> > Still seeing this just after quotas get turned on ext4. First seen in
> > 2.6.36-mmotm1022, but problem has apparently been there since
> > 2.6.36-rc5-mmotm0922 (oldest kernel I have lying around).
> Thanks for the report. In fact, it is a false positive caused by the fact
> that EXT4(inode)->i_data_sem for quota file inode would need a special
> locking class (or subclass) but does not have one. I'll have a look into
> implementing that sometime next week hopefully.
> > [ 48.967833] =======================================================
> > [ 48.968162] [ INFO: possible circular locking dependency detected ]
> > [ 48.968411] 2.6.37-rc1-mmotm1109 #1
I haven't spotted the commit that fixed it, but I'm assuming it's in there
now, as I am not seeing it on 2.6.37-rc3-mmotm1123, thanks.
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2010-11-25 5:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 23:31 mmotm 2010-11-09-15-31 uploaded akpm
2010-11-10 1:01 ` mmotm 2010-11-09-15-31 uploaded (sound/soc/soc-core.c) Randy Dunlap
2010-11-11 19:25 ` mmotm 2010-11-09 - lockdep splat in ext4/quota code Valdis.Kletnieks
2010-11-12 23:33 ` Jan Kara
2010-11-25 5:35 ` Valdis.Kletnieks [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=28481.1290663350@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.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;
as well as URLs for NNTP newsgroup(s).