From: "agentzh at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/30393] Lockdep error in _stp_ctl_work_callback()/wake_up_interruptible() on a fedora debug kernel
Date: Thu, 18 May 2023 17:43:50 +0000 [thread overview]
Message-ID: <bug-30393-6586-Jt737WED1r@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30393-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30393
--- Comment #4 from agentzh <agentzh at gmail dot com> ---
Here's my best theory: a user process has grabbed the mm map lock, and in its
critical section, stap runtime's ctl work timer is fired; and inside the ctl
work callback, stap calls wake_up_interruptible(), which may try to trigger
scheduler context switches and hence that lockdep error "Illegal context switch
in RCU-bh read-side critical section!".
__wake_up_common_lock() appears in the lockdep backtrace, which is indeed
called from __wake_up(), which is wake_up_interruptible(). Furthermore, both
_stp_request_exit and _stp_ctl_work_callback are in the lockdep backtrace.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-05-18 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 21:47 [Bug runtime/30393] New: New lockdep error " agentzh at gmail dot com
2023-04-27 17:36 ` [Bug runtime/30393] " agentzh at gmail dot com
2023-04-28 0:48 ` agentzh at gmail dot com
2023-04-30 21:29 ` [Bug runtime/30393] Lockdep error in _stp_ctl_work_callback()/_stp_request_exit() " agentzh at gmail dot com
2023-05-01 18:19 ` agentzh at gmail dot com
2023-05-01 18:19 ` [Bug runtime/30393] Lockdep error in _stp_ctl_work_callback()/wake_up_interruptible() " agentzh at gmail dot com
2023-05-18 17:43 ` agentzh at gmail dot com [this message]
2023-05-18 17:47 ` agentzh at gmail dot com
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=bug-30393-6586-Jt737WED1r@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).