This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:20
- From: Keshavamurthy Anil S <anil dot s dot keshavamurthy at intel dot com>
- To: Keshavamurthy Anil S <anil dot s dot keshavamurthy at intel dot com>
- Cc: Systemtap <systemtap at sources dot redhat dot com>
- Date: Fri, 8 Sep 2006 11:37:42 -0700
- Subject: Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:20
- References: <20060908110946.B9235@unix-os.sc.intel.com>
- Reply-to: Keshavamurthy Anil S <anil dot s dot keshavamurthy at intel dot com>
On Fri, Sep 08, 2006 at 11:09:48AM -0700, Keshavamurthy Anil S wrote:
More debugging resulted that Systemtap generated code is
calling down_read() in the probe handler code path.
down_read()->might_sleep()->__might_sleep(__FILE__, __LINE__);
If CONFIG_DEBUG_SPINLOCK_SLEEP is turned off, then we don;t see the dump.
But Red Hat's default kernel config has this option turned on.
Overall, looks to me that Systemtap in the first place should not use
rw_semaphore calls in the probe handler code path.
I am happy to provide more info if any one needs.
thanks,
Anil