From: Pavel Machek <pavel@ucw.cz>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
"Paul E. McKenney" <paulmck@kernel.org>,
frederic@kernel.org, quic_neeraju@quicinc.com,
joel@joelfernandes.org, josh@joshtriplett.org,
boqun.feng@gmail.com, rcu@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 5.10] rcu: Mark rcu_cpu_kthread() accesses to ->rcu_cpu_has_work
Date: Wed, 12 Jul 2023 12:11:56 +0200 [thread overview]
Message-ID: <ZK58bFy80qmsRI/c@duo.ucw.cz> (raw)
In-Reply-To: <20230702195806.1793552-1-sashal@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
On Sun 2023-07-02 15:58:06, Sasha Levin wrote:
> From: "Paul E. McKenney" <paulmck@kernel.org>
>
> [ Upstream commit a24c1aab652ebacf9ea62470a166514174c96fe1 ]
>
> The rcu_data structure's ->rcu_cpu_has_work field can be modified by
> any CPU attempting to wake up the rcuc kthread. Therefore, this commit
> marks accesses to this field from the rcu_cpu_kthread() function.
>
> This data race was reported by KCSAN. Not appropriate for backporting
> due to failure being unlikely.
Please drop.
Best regards,
Pavel
--
People of Russia, stop Putin before his war on Ukraine escalates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2023-07-12 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 19:58 [PATCH AUTOSEL 5.10] rcu: Mark rcu_cpu_kthread() accesses to ->rcu_cpu_has_work Sasha Levin
2023-07-12 10:11 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-09 14:55 Sasha Levin
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=ZK58bFy80qmsRI/c@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.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