From: Li Zefan <lizf@cn.fujitsu.com>
To: Divyesh Shah <dpshah@google.com>
Cc: Gui Jianfeng <guijianfeng@cn.fujitsu.com>,
Vivek Goyal <vgoyal@redhat.com>,
Jens Axboe <jens.axboe@oracle.com>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: lockdep warning on block tree for-2.6.35 branch
Date: Fri, 16 Apr 2010 11:57:11 +0800 [thread overview]
Message-ID: <4BC7E017.4020002@cn.fujitsu.com> (raw)
In-Reply-To: <y2gaf41c7c41004152051w5628eb9fja2159c0eac93cb26@mail.gmail.com>
Divyesh Shah :
> Hi Gui,
> Thanks for the report. I can reproduce this and have a patch that
> fixes it and makes the warning go away. My understanding of what was
> happening is that the stats_lock for the root cfqg was not getting
> initialized and hence was missing the static lock_class_key
> declaration. This is because we call blkio_group_init() only when
> dynamically allocating new cfqg which does not cover the root cfqg.
> I'll send out the patch next.
>
We just found out the cause and was about to make a fix. :)
-- Li
prev parent reply other threads:[~2010-04-16 3:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 1:40 lockdep warning on block tree for-2.6.35 branch Gui Jianfeng
2010-04-16 3:51 ` Divyesh Shah
2010-04-16 3:57 ` Li Zefan [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=4BC7E017.4020002@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=dpshah@google.com \
--cc=guijianfeng@cn.fujitsu.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.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