From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
linke li <lilinke99@qq.com>,
joel@joelfernandes.org, boqun.feng@gmail.com, dave@stgolabs.net,
frederic@kernel.org, jiangshanlai@gmail.com,
josh@joshtriplett.org, linux-kernel@vger.kernel.org,
mathieu.desnoyers@efficios.com, qiang.zhang1211@gmail.com,
quic_neeraju@quicinc.com, rcu@vger.kernel.org
Subject: Re: [PATCH] rcutorture: Fix rcu_torture_pipe_update_one()/rcu_torture_writer() data race and concurrency bug
Date: Wed, 6 Mar 2024 13:55:04 -0500 [thread overview]
Message-ID: <20240306135504.2b3872ef@gandalf.local.home> (raw)
In-Reply-To: <CAHk-=wgG6Dmt1JTXDbrbXh_6s2yLjL=9pHo7uv0==LHFD+aBtg@mail.gmail.com>
On Wed, 6 Mar 2024 10:43:25 -0800
Linus Torvalds <torvalds@linux-foundation.org> wrote:
Thanks for the history lesson ;-)
> So yes, READ_ONCE/WRITE_ONCE do control "tearing", but realistically,
> it was always only about the "complex values" kind of tearing that the
> old ACCESS_ONCE() model silently and incorrectly allowed.
Now, are you OK with an addition of ADD_ONCE() and/or INC_ONCE()? So that we
don't have to look at:
WRITE_ONCE(a, READ_ONCE(a) + 1);
?
-- Steve
next prev parent reply other threads:[~2024-03-06 18:53 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 10:54 linke li
2024-03-04 16:19 ` Joel Fernandes
2024-03-04 17:14 ` Paul E. McKenney
2024-03-04 19:10 ` Joel Fernandes
2024-03-04 19:44 ` Paul E. McKenney
2024-03-04 20:13 ` Joel Fernandes
2024-03-04 20:47 ` Paul E. McKenney
2024-03-05 3:30 ` linke
2024-03-05 6:24 ` linke li
2024-03-06 15:37 ` Steven Rostedt
2024-03-06 17:36 ` Paul E. McKenney
2024-03-06 18:01 ` Steven Rostedt
2024-03-06 18:09 ` Paul E. McKenney
2024-03-06 18:20 ` Steven Rostedt
2024-03-06 18:43 ` Linus Torvalds
2024-03-06 18:55 ` Steven Rostedt [this message]
2024-03-06 19:01 ` Linus Torvalds
2024-03-06 19:27 ` Linus Torvalds
2024-03-06 19:47 ` Steven Rostedt
2024-03-06 20:06 ` Linus Torvalds
2024-03-07 13:20 ` Steven Rostedt
2024-03-07 16:12 ` Steven Rostedt
2024-03-06 19:27 ` Steven Rostedt
2024-03-06 19:46 ` Linus Torvalds
2024-03-06 20:20 ` Linus Torvalds
2024-03-07 2:29 ` Paul E. McKenney
2024-03-07 2:43 ` Linus Torvalds
2024-03-07 2:49 ` Linus Torvalds
2024-03-07 3:21 ` Paul E. McKenney
2024-03-07 3:06 ` Paul E. McKenney
2024-03-07 3:06 ` Mathieu Desnoyers
2024-03-07 3:37 ` Paul E. McKenney
2024-03-07 5:44 ` Joel Fernandes
2024-03-07 19:05 ` Paul E. McKenney
2024-03-07 13:53 ` Mathieu Desnoyers
2024-03-07 19:47 ` Paul E. McKenney
2024-03-07 19:53 ` Mathieu Desnoyers
2024-03-08 0:58 ` Paul E. McKenney
2024-03-07 20:00 ` Linus Torvalds
2024-03-07 20:57 ` Paul E. McKenney
2024-03-07 21:40 ` Julia Lawall
2024-03-07 22:09 ` Linus Torvalds
2024-03-08 0:55 ` 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=20240306135504.2b3872ef@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=boqun.feng@gmail.com \
--cc=dave@stgolabs.net \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=lilinke99@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=qiang.zhang1211@gmail.com \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®