From: "Paul E. McKenney" <paulmck@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, rcu@vger.kernel.org,
urezki@gmail.com, tglx@linutronix.de,
linuxppc-dev@lists.ozlabs.org, mingo@kernel.org, dja@axtens.net
Subject: [GIT PULL] Fix kprobes issue by moving RCU-tasks initialization earlier
Date: Mon, 4 Jan 2021 10:19:34 -0800 [thread overview]
Message-ID: <20210104181934.GA16612@paulmck-ThinkPad-P72> (raw)
Hello, Linus,
This fix is for a regression in the v5.10 merge window, but it was
reported quite late in the v5.10 process, plus generating and testing
the fix took some time.
The regression is due to 36dadef23fcc ("kprobes: Init kprobes in
early_initcall") which on powerpc can use RCU Tasks before initialization,
resulting in boot failures. The fix is straightforward, simply moving
initialization of RCU Tasks before the early_initcall()s. The fix has
been exposed to -next and kbuild test robot testing, and has been
tested by the PowerPC guys.
The following changes since commit 0477e92881850d44910a7e94fc2c46f96faa131f:
Linux 5.10-rc7 (2020-12-06 14:25:12 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/urgent
for you to fetch changes up to 1b04fa9900263b4e217ca2509fd778b32c2b4eb2:
rcu-tasks: Move RCU-tasks initialization to before early_initcall() (2020-12-14 15:31:13 -0800)
----------------------------------------------------------------
Uladzislau Rezki (Sony) (1):
rcu-tasks: Move RCU-tasks initialization to before early_initcall()
include/linux/rcupdate.h | 6 ++++++
init/main.c | 1 +
kernel/rcu/tasks.h | 25 +++++++++++++++++++++----
3 files changed, 28 insertions(+), 4 deletions(-)
next reply other threads:[~2021-01-04 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 18:19 Paul E. McKenney [this message]
2021-01-04 19:02 ` [GIT PULL] Fix kprobes issue by moving RCU-tasks initialization earlier pr-tracker-bot
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=20210104181934.GA16612@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=dja@axtens.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=urezki@gmail.com \
/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