From: Guillaume Morin <guillaume@morinfr.org>
To: "Paul E. McKenney" <paulmck@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: call_rcu data race patch
Date: Sat, 18 Sep 2021 09:08:38 +0200 [thread overview]
Message-ID: <20210918070836.GA19555@bender.morinfr.org> (raw)
In-Reply-To: <20210918040035.GX4156@paulmck-ThinkPad-P17-Gen-1>
On 17 Sep 21:00, Paul E. McKenney wrote:
> That is them! There are some flags that control their activities:
>
> o rcu_data structure's ->nocb_gp_sleep field (rcuog)
> o rcu_data structure's ->nocb_cb_sleep field (rcuoc)
From the same kdump:
crash> pd rcu_data:all | grep -E 'nocb_cb_sleep|nocb_gp_sleep|per_cpu'
per_cpu(rcu_data, 0) = $69 = {
nocb_gp_sleep = 0 '\000',
nocb_cb_sleep = false,
per_cpu(rcu_data, 1) = $70 = {
nocb_gp_sleep = 1 '\001',
nocb_cb_sleep = true,
per_cpu(rcu_data, 2) = $71 = {
nocb_gp_sleep = 0 '\000',
nocb_cb_sleep = true,
per_cpu(rcu_data, 3) = $72 = {
nocb_gp_sleep = 0 '\000',
nocb_cb_sleep = true,
per_cpu(rcu_data, 4) = $73 = {
nocb_gp_sleep = 1 '\001',
nocb_cb_sleep = true,
per_cpu(rcu_data, 5) = $74 = {
nocb_gp_sleep = 0 '\000',
nocb_cb_sleep = true,
per_cpu(rcu_data, 6) = $75 = {
nocb_gp_sleep = 0 '\000',
nocb_cb_sleep = true,
per_cpu(rcu_data, 7) = $76 = {
nocb_gp_sleep = 0 '\000',
nocb_cb_sleep = true,
per_cpu(rcu_data, 8) = $77 = {
nocb_gp_sleep = 1 '\001',
nocb_cb_sleep = true,
per_cpu(rcu_data, 9) = $78 = {
nocb_gp_sleep = 0 '\000',
nocb_cb_sleep = true,
per_cpu(rcu_data, 10) = $79 = {
nocb_gp_sleep = 0 '\000',
nocb_cb_sleep = true,
per_cpu(rcu_data, 11) = $80 = {
nocb_gp_sleep = 0 '\000',
nocb_cb_sleep = true,
per_cpu(rcu_data, 12) = $81 = {
nocb_gp_sleep = 1 '\001',
nocb_cb_sleep = true,
per_cpu(rcu_data, 13) = $82 = {
nocb_gp_sleep = 0 '\000',
nocb_cb_sleep = true,
per_cpu(rcu_data, 14) = $83 = {
nocb_gp_sleep = 0 '\000',
nocb_cb_sleep = true,
per_cpu(rcu_data, 15) = $84 = {
nocb_gp_sleep = 0 '\000',
nocb_cb_sleep = true,
per_cpu(rcu_data, 16) = $85 = {
nocb_gp_sleep = 1 '\001',
nocb_cb_sleep = true,
per_cpu(rcu_data, 17) = $86 = {
nocb_gp_sleep = 0 '\000',
nocb_cb_sleep = true,
crash>
--
Guillaume Morin <guillaume@morinfr.org>
next prev parent reply other threads:[~2021-09-18 7:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210917191555.GA2198@bender.morinfr.org>
2021-09-17 21:11 ` call_rcu data race patch Paul E. McKenney
2021-09-17 21:34 ` Guillaume Morin
2021-09-17 22:07 ` Paul E. McKenney
2021-09-18 0:39 ` Guillaume Morin
2021-09-18 4:00 ` Paul E. McKenney
2021-09-18 7:08 ` Guillaume Morin [this message]
2021-09-19 16:35 ` Paul E. McKenney
2021-09-20 16:05 ` Guillaume Morin
2021-09-22 19:14 ` Guillaume Morin
2021-09-22 19:24 ` Paul E. McKenney
2021-09-27 15:38 ` Guillaume Morin
2021-09-27 16:10 ` Paul E. McKenney
2021-09-27 16:49 ` Guillaume Morin
2021-09-27 21:46 ` Paul E. McKenney
2021-09-30 13:50 ` Guillaume Morin
2021-11-18 18:41 ` Daniel Vacek
2021-11-18 22:59 ` Paul E. McKenney
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=20210918070836.GA19555@bender.morinfr.org \
--to=guillaume@morinfr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.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