From: Valdis Kletnieks <valdis.kletnieks@vt.edu>
To: Jens Axboe <axboe@kernel.dk>, Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: next-20120604 WARNING: at block/blk-cgroup.c:867
Date: Tue, 05 Jun 2012 23:23:40 -0400 [thread overview]
Message-ID: <3785.1338953020@turing-police.cc.vt.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1997 bytes --]
Seen in my dmesg at boot:
[ 0.682289] cryptomgr_test (30) used greatest stack depth: 6344 bytes left
[ 0.683288] io scheduler noop registered
[ 0.683292] io scheduler deadline registered
[ 0.683294] ------------[ cut here ]------------
[ 0.683300] WARNING: at block/blk-cgroup.c:867 blkcg_policy_register+0x41/0x10a()
[ 0.683302] Hardware name: Latitude E6500
[ 0.683305] Modules linked in:
[ 0.683308] Pid: 1, comm: swapper/0 Not tainted 3.5.0-rc1-next-20120604 #25
[ 0.683310] Call Trace:
[ 0.683316] [<ffffffff8102c7ce>] warn_slowpath_common+0x7e/0x96
[ 0.683320] [<ffffffff8102c7fb>] warn_slowpath_null+0x15/0x17
[ 0.683324] [<ffffffff8123d8a2>] blkcg_policy_register+0x41/0x10a
[ 0.683329] [<ffffffff81d4caca>] ? deadline_init+0x12/0x12
[ 0.683332] [<ffffffff81d4cb0c>] cfq_init+0x42/0x9f
[ 0.683337] [<ffffffff810001fa>] do_one_initcall+0x7a/0x130
[ 0.683341] [<ffffffff81d2fbdc>] do_initcalls+0xa7/0xc9
[ 0.683344] [<ffffffff81d2f5ed>] ? do_early_param+0x87/0x87
[ 0.683348] [<ffffffff81d2fcd4>] kernel_init+0xd6/0x147
[ 0.683352] [<ffffffff81603bb4>] kernel_thread_helper+0x4/0x10
[ 0.683356] [<ffffffff81055f99>] ? finish_task_switch+0x38/0x103
[ 0.683360] [<ffffffff815fc61d>] ? retint_restore_args+0xe/0xe
[ 0.683364] [<ffffffff81d2fbfe>] ? do_initcalls+0xc9/0xc9
[ 0.683367] [<ffffffff81603bb0>] ? gs_change+0xb/0xb
[ 0.683376] ---[ end trace e93713a9d40cd06c ]---
[ 0.683378] start plist test
[ 0.687084] end plist test
Probably relevant...
% zgrep CGR /proc/config.gz
CONFIG_CGROUPS=y
CONFIG_CGROUP_DEBUG=y
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_CGROUP_MEM_RES_CTLR=y
CONFIG_CGROUP_MEM_RES_CTLR_SWAP=y
CONFIG_CGROUP_MEM_RES_CTLR_SWAP_ENABLED=y
# CONFIG_CGROUP_MEM_RES_CTLR_KMEM is not set
CONFIG_CGROUP_PERF=y
CONFIG_CGROUP_SCHED=y
CONFIG_BLK_CGROUP=y
# CONFIG_DEBUG_BLK_CGROUP is not set
# CONFIG_NET_CLS_CGROUP is not set
CONFIG_NETPRIO_CGROUP=m
[-- Attachment #2: Type: application/pgp-signature, Size: 865 bytes --]
next reply other threads:[~2012-06-06 3:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 3:23 Valdis Kletnieks [this message]
2012-06-06 3:37 ` valdis.kletnieks
2012-06-06 6:37 ` Jens Axboe
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=3785.1338953020@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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
all inboxes | Powered by JetHome®