From: Sasha Levin <sasha.levin@oracle.com>
To: oprofile-list@lists.sf.net
Cc: robert.richter@amd.com, LKML <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>
Subject: oprofile: calling debug_smp_processor_id from preemptible code
Date: Sat, 10 May 2014 20:13:53 -0400 [thread overview]
Message-ID: <536EC0C1.3090105@oracle.com> (raw)
Hi all,
While fuzzing with trinity inside a KVM tools guest running the latest -next
kernel I've stumbled on the following spew:
[ 358.852124] BUG: using smp_processor_id() in preemptible [00000000] code: kworker/24:1/6824
[ 358.858753] caller is debug_smp_processor_id+0x17/0x20
[ 358.859777] CPU: 23 PID: 6824 Comm: kworker/24:1 Not tainted 3.15.0-rc4-next-2014050
8-sasha-00020-gec9304b-dirty #452
[ 358.862844] Workqueue: events wq_sync_buffer
[ 358.863786] ffffffffa97d8801 ffff880585e05cd8 ffffffffa853ba9a 0000000000000002
[ 358.865500] 0000000000000017 ffff880585e05d08 ffffffffa5b41439 ffff8805871d3bc0
[ 358.866717] 0000000000000018 ffff8805871de000 0000000000000000 ffff880585e05d18
[ 358.868075] Call Trace:
[ 358.868513] dump_stack (lib/dump_stack.c:52)
[ 358.869319] check_preemption_disabled (arch/x86/include/asm/preempt.h:80 lib/smp_processor_id.c:49)
[ 358.870679] debug_smp_processor_id (lib/smp_processor_id.c:57)
[ 358.871906] wq_sync_buffer (arch/x86/oprofile/../../../drivers/oprofile/cpu_buffer.c:454)
[ 358.872974] process_one_work (kernel/workqueue.c:2227 include/linux/jump_label.h:105 include/trace/events/workqueue.h:111 kernel/workqueue.c:2232)
[ 358.873891] ? process_one_work (include/linux/workqueue.h:186 kernel/workqueue.c:611 kernel/workqueue.c:638 kernel/workqueue.c:2220)
[ 358.874796] worker_thread (kernel/workqueue.c:2354)
[ 358.875830] ? rescuer_thread (kernel/workqueue.c:2303)
[ 358.876948] kthread (kernel/kthread.c:210)
[ 358.878202] ? kthread_create_on_node (kernel/kthread.c:176)
[ 358.879523] ret_from_fork (arch/x86/kernel/entry_64.S:553)
[ 358.880744] ? kthread_create_on_node (kernel/kthread.c:176)
Thanks,
Sasha
reply other threads:[~2014-05-11 0:14 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=536EC0C1.3090105@oracle.com \
--to=sasha.levin@oracle.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oprofile-list@lists.sf.net \
--cc=robert.richter@amd.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