Re: [BUG] perf and kmemcheck : fatal combination

[Eric Dumazet]

Le mardi 26 avril 2011 Ã 14:33 +0200, Peter Zijlstra a Ãcrit :
> On Tue, 2011-04-26 at 14:27 +0200, Eric Dumazet wrote:
> > Thats far from trivial, maybe because we dont have NOTRACK api for
> > percpu allocations ? 
> 
> We can't use per-cpu allocations from NMI context because of the same
> problem, per-cpu uses vmalloc and vmalloc needs faults. Hence that
> shouldn't be a problem.
> 
> It looks like you covered most of it though, the buffer and the
> callchain stuff, aside from that it should only use some static data.
> 
> Pekka, what does kmemcheck do for .data and .bss things?

Hmm, maybe I have a problem because of the WARN_ON in kmemcheck and my
boot had "log_buf_len=32M", so kmemcheck was called again


I am now trying to remve the line 634 from
arch/x86/mm/kmemcheck/kmemcheck.c

[ 4564.554310] WARNING: at arch/x86/mm/kmemcheck/kmemcheck.c:634 kmemcheck_fault+0xa9/0xc0()
[ 4564.554312] Hardware name: ProLiant BL460c G6
[ 4564.554313] Modules linked in: nfsd lockd auth_rpcgss sunrpc tg3 libphy sg [last unloaded: x_tables]
[ 4564.554319] Pid: 4276, comm: perf Not tainted 2.6.39-rc4-00369-g23cf772-dirty #561
[ 4564.554320] Call Trace:
[ 4564.554322]  <NMI>  [<ffffffff8102ac39>] ? kmemcheck_fault+0xa9/0xc0
[ 4564.554329]  [<ffffffff810427db>] warn_slowpath_common+0x8b/0xc0
[ 4564.554331]  [<ffffffff81042825>] warn_slowpath_null+0x15/0x20
[ 4564.554333]  [<ffffffff8102ac39>] kmemcheck_fault+0xa9/0xc0
[ 4564.554337]  [<ffffffff8147ca4b>] do_page_fault+0x1fb/0x560
[ 4564.554342]  [<ffffffff811d0289>] ? put_dec+0x59/0x60
[ 4564.554344]  [<ffffffff811d0591>] ? number+0x301/0x330
[ 4564.554347]  [<ffffffff8147a48f>] page_fault+0x1f/0x30
[ 4564.554352]  [<ffffffff8124dce5>] ? vt_console_print+0x85/0x360
[ 4564.554355]  [<ffffffff8124dcda>] ? vt_console_print+0x7a/0x360
[ 4564.554358]  [<ffffffff81043159>] __call_console_drivers+0x89/0xa0
[ 4564.554360]  [<ffffffff810431bb>] _call_console_drivers+0x4b/0x80
[ 4564.554362]  [<ffffffff810432d7>] console_unlock+0xe7/0x1e0
[ 4564.554365]  [<ffffffff8104388e>] vprintk+0x1ee/0x4a0
[ 4564.554368]  [<ffffffff8102ac39>] ? kmemcheck_fault+0xa9/0xc0
[ 4564.554370]  [<ffffffff81043ba7>] printk+0x67/0x70
[ 4564.554372]  [<ffffffff8102ac39>] ? kmemcheck_fault+0xa9/0xc0
[ 4564.554375]  [<ffffffff81042789>] warn_slowpath_common+0x39/0xc0
[ 4564.554377]  [<ffffffff81042825>] warn_slowpath_null+0x15/0x20
[ 4564.554379]  [<ffffffff8102ac39>] kmemcheck_fault+0xa9/0xc0
[ 4564.554381]  [<ffffffff8147ca4b>] do_page_fault+0x1fb/0x560
[ 4564.554384]  [<ffffffff8101167b>] ? intel_pmu_drain_bts_buffer+0x2b/0x170
[ 4564.554387]  [<ffffffff8147a48f>] page_fault+0x1f/0x30
[ 4564.554390]  [<ffffffff8100ef42>] ? x86_perf_event_update+0x12/0x70
[ 4564.554392]  [<ffffffff810104b1>] ? intel_pmu_save_and_restart+0x11/0x20
[ 4564.554394]  [<ffffffff81012e84>] intel_pmu_handle_irq+0x1d4/0x420
[ 4564.554397]  [<ffffffff8147b570>] perf_event_nmi_handler+0x50/0xc0
[ 4564.554399]  [<ffffffff8147cfa3>] notifier_call_chain+0x53/0x80
[ 4564.554401]  [<ffffffff8147d018>] __atomic_notifier_call_chain+0x48/0x70
[ 4564.554404]  [<ffffffff8147d051>] atomic_notifier_call_chain+0x11/0x20
[ 4564.554406]  [<ffffffff8147d08e>] notify_die+0x2e/0x30
[ 4564.554407]  [<ffffffff8147a8af>] do_nmi+0x4f/0x200
[ 4564.554409]  [<ffffffff8147a6ea>] nmi+0x1a/0x20
[ 4564.554411]  [<ffffffff8100fd4d>] ? intel_pmu_enable_all+0x9d/0x110



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