From: Sasha Levin <sasha.levin@oracle.com>
To: Greg KH <greg@kroah.com>, Tejun Heo <tj@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: kernfs: WARNING: CPU: 59 PID: 10414 at lib/debugobjects.c:260
Date: Sun, 22 Dec 2013 15:46:41 -0500 [thread overview]
Message-ID: <52B74FB1.7070306@oracle.com> (raw)
Hi all,
While fuzzing with trinity inside a KVM tools guest running latest -next kernel, I've stumbled on
the following spew.
Beyond regular trinity fuzzing, the machine was in the middle of attempting to offline all of it's
cpus (64 of them).
[ 645.148744] WARNING: CPU: 59 PID: 10414 at lib/debugobjects.c:260 debug_print_object
+0x8d/0xb0()
[ 645.150844] ODEBUG: free active (active state 0) object type: timer_list hint: delay
ed_work_timer_fn+0x0/0x20
[ 645.152178] Modules linked in:
[ 645.152699] CPU: 59 PID: 10414 Comm: sh Tainted: G W 3.13.0-rc4-next-20131
220-sasha-00013-gf9a57f1-dirty #6
[ 645.154113] 0000000000000104 ffff88001a74fa68 ffffffff845d3d3c ffffffff858006ee
[ 645.155294] ffff88001a74fab8 ffff88001a74faa8 ffffffff8112f93c ffff88001a74fad8
[ 645.155294] ffffffff8594fab2 ffff880168f10a10 ffffffff86068c00 ffffffff8891eaf8
[ 645.157180] Call Trace:
[ 645.157697] [<ffffffff845d3d3c>] dump_stack+0x52/0x7f
[ 645.157975] [<ffffffff8112f93c>] warn_slowpath_common+0x8c/0xc0
[ 645.158744] [<ffffffff8112fa26>] warn_slowpath_fmt+0x46/0x50
[ 645.158744] [<ffffffff81adcd2d>] debug_print_object+0x8d/0xb0
[ 645.158744] [<ffffffff81153130>] ? __queue_work+0x3f0/0x3f0
[ 645.158744] [<ffffffff81add535>] __debug_check_no_obj_freed+0xa5/0x220
[ 645.158744] [<ffffffff8107e346>] ? cpuid4_cache_sysfs_exit+0x46/0xc0
[ 645.158744] [<ffffffff8107e346>] ? cpuid4_cache_sysfs_exit+0x46/0xc0
[ 645.158744] [<ffffffff81add6c5>] debug_check_no_obj_freed+0x15/0x20
[ 645.158744] [<ffffffff812ae4bf>] kfree+0x21f/0x2e0
[ 645.158744] [<ffffffff8107e346>] cpuid4_cache_sysfs_exit+0x46/0xc0
[ 645.158744] [<ffffffff8107ebea>] cache_remove_dev+0x11a/0x130
[ 645.158744] [<ffffffff8107f128>] cacheinfo_cpu_callback+0x78/0x90
[ 645.158744] [<ffffffff845e027e>] notifier_call_chain+0xee/0x130
[ 645.158744] [<ffffffff8116273e>] __raw_notifier_call_chain+0xe/0x10
[ 645.158744] [<ffffffff8112fbe0>] __cpu_notify+0x20/0x40
[ 645.158744] [<ffffffff8112fc15>] cpu_notify_nofail+0x15/0x30
[ 645.158744] [<ffffffff845caf75>] _cpu_down+0x195/0x2e0
[ 645.158744] [<ffffffff8112fc97>] ? cpu_maps_update_begin+0x17/0x20
[ 645.158744] [<ffffffff8207f745>] ? device_offline+0x55/0xd0
[ 645.158744] [<ffffffff845c9825>] ? klist_next+0xf5/0x120
[ 645.158744] [<ffffffff845d67cd>] ? mutex_trylock+0x1fd/0x270
[ 645.158744] [<ffffffff845cb0f6>] cpu_down+0x36/0x50
[ 645.158744] [<ffffffff82086034>] cpu_subsys_offline+0x14/0x20
[ 645.158744] [<ffffffff8207f772>] device_offline+0x82/0xd0
[ 645.158744] [<ffffffff820806d8>] online_store+0x58/0x80
[ 645.158744] [<ffffffff8207e6d0>] dev_attr_store+0x20/0x30
[ 645.158744] [<ffffffff8135d62f>] sysfs_kf_write+0x4f/0x70
[ 645.158744] [<ffffffff8136160b>] kernfs_fop_write+0xdb/0x140
[ 645.158744] [<ffffffff812d51a3>] vfs_write+0xf3/0x1e0
[ 645.158744] [<ffffffff812d5392>] SyS_write+0x62/0xa0
[ 645.158744] [<ffffffff845e4e90>] tracesys+0xdd/0xe2
Thanks,
Sasha
reply other threads:[~2013-12-22 20:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52B74FB1.7070306@oracle.com \
--to=sasha.levin@oracle.com \
--cc=greg@kroah.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.