[Bug runtime/14630] intermittent crash in lookup_bad_addr

["fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=14630

--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> 2012-09-26 17:50:25 UTC ---
With $SYSTEMTAP_SYNC, another run produced a similar crash:

stap_2e79445e6d8698522a9f86c95ee78935_4327: systemtap: 2.0/0.152, base:
ffffffffa042c000, memory: 57data/29text/20ctx/2058net/34alloc kb, probes: 28
stap_67912742e5bc7aca566eb18b6434082a__5618: systemtap: 2.0/0.152, base:
ffffffffa0449000, memory: 78data/59text/20ctx/2058net/178alloc kb, probes: 28
BUG: sleeping function called from invalid context at arch/x86/mm/fault.c:1112
in_atomic(): 0, irqs_disabled(): 1, pid: 5618, name: stapio
3 locks held by stapio/5618:
 #0:  (&rq->lock){-.-.-.}, at: [<ffffffff8152e355>] thread_return+0x680/0x7db
 #1:  (& global.s_hits_lock){......}, at: [<ffffffffa0449e75>]
stp_lock_probe+0x55/0xc0 [stap_67912742e5bc7aca566eb18b6434082a__5618]
 #2:  (&mm->mmap_sem){++++++}, at: [<ffffffff81044489>]
__do_page_fault+0xf9/0x4e0
irq event stamp: 102228
hardirqs last  enabled at (102227): [<ffffffff81531230>]
_spin_unlock_irqrestore+0x40/0x80
hardirqs last disabled at (102228): [<ffffffff8153152f>]
_spin_lock_irq+0x1f/0x80
softirqs last  enabled at (101522): [<ffffffff81077831>]
__do_softirq+0x151/0x210
softirqs last disabled at (101261): [<ffffffff8100c30c>] call_softirq+0x1c/0x30
Pid: 5618, comm: stapio Not tainted 2.6.32-279.5.2.el6.x86_64.debug #1
Call Trace:
 [<ffffffff810ab580>] ? print_irqtrace_events+0xd0/0xe0
 [<ffffffff810582b7>] ? __might_sleep+0xf7/0x130
 [<ffffffff810444a4>] ? __do_page_fault+0x114/0x4e0
 [<ffffffff810aec3f>] ? check_irq_usage+0x9f/0xf0
 [<ffffffff810b07aa>] ? __lock_acquire+0xaca/0x1570
 [<ffffffff810396d8>] ? pvclock_clocksource_read+0x58/0xd0
 [<ffffffffa044a1cd>] ? lookup_bad_addr+0xcd/0xe0
[stap_67912742e5bc7aca566eb18b6434082a__5618]
 [<ffffffff810387cc>] ? kvm_clock_read+0x1c/0x20
 [<ffffffff81012da9>] ? sched_clock+0x9/0x10
 [<ffffffff8109e885>] ? sched_clock_local+0x25/0x90


where the instruction in question points to the _read_unlock() call.
I wonder if perhaps this is a lockdep problem.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.