From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/21859] on rawhide, the context.exp test case causes a kernel warning
Date: Fri, 28 Jul 2017 15:45:00 -0000 [thread overview]
Message-ID: <bug-21859-6586-8Pb2h3MZjC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21859-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21859
--- Comment #1 from David Smith <dsmith at redhat dot com> ---
The following kernel commit changed module_kallsyms_on_each_symbol(), which is
called by kallsyms_on_each_symbol, to quit doing RCU-style module list
traversal and require the module_mutex:
====
commit 0be964be0d45084245673c971d72a4b51690231d
Author: Peter Zijlstra <peterz@infradead.org>
Date: Wed May 27 11:09:35 2015 +0930
module: Sanitize RCU usage and locking
Currently the RCU usage in module is an inconsistent mess of RCU and
RCU-sched, this is broken for CONFIG_PREEMPT where synchronize_rcu()
does not imply synchronize_sched().
Most usage sites use preempt_{dis,en}able() which is RCU-sched, but
(most of) the modification sites use synchronize_rcu(). With the
exception of the module bug list, which actually uses RCU.
Convert everything over to RCU-sched.
Furthermore add lockdep asserts to all sites, because it's not at all
clear to me the required locking is observed, esp. on exported
functions.
====
It looks like this patch was first included in kernel version 4.2. So, we'll
have to hold the module_mutex when calling kallsyms_on_each_symbol().
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2017-07-28 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 15:31 [Bug runtime/21859] New: " dsmith at redhat dot com
2017-07-28 15:45 ` dsmith at redhat dot com [this message]
2017-07-28 16:19 ` [Bug runtime/21859] " dsmith at redhat 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-21859-6586-8Pb2h3MZjC@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).