linux-kernel - oprofile: calling debug_smp_processor

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <536EC0C1.3090105@oracle.com>
Date:	Sat, 10 May 2014 20:13:53 -0400
From:	Sasha Levin <sasha.levin@...cle.com>
To:	oprofile-list@...ts.sf.net
CC:	robert.richter@....com, LKML <linux-kernel@...r.kernel.org>,
	Dave Jones <davej@...hat.com>
Subject: oprofile: calling debug_smp_processor_id from preemptible code

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/