From: "Paul E. McKenney" <paulmck@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Anna-Maria Behnsen <anna-maria@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
Thomas Gleixner <tglx@kernel.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
linux-kernel@vger.kernel.org, kernel-team@meta.com,
Benjamin LaHaise <bcrl@kvack.org>,
Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
linux-aio@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RFC 2/9] aio: Use accessor for hrtimer_sleeper ->task field
Date: Fri, 31 Jul 2026 10:40:44 -0700 [thread overview]
Message-ID: <0f8ddd97-89e1-45c8-a779-e56adcde4098@paulmck-laptop> (raw)
In-Reply-To: <20260731-ritzen-ratgeber-fastnacht-519674d2de1d@brauner>
On Fri, Jul 31, 2026 at 02:57:57PM +0200, Christian Brauner wrote:
> On 2026-07-30 17:40 -0700, Paul E. McKenney wrote:
> > The hrtimer_sleeper structure's ->task field is used as a flag to indicate
> > that the associated hrtimer has expired. This means that the hrtimer
> > handler can be storing to this field while other code is loading from it
> > to check for expiry. Note that additional races appear for hrtimers that
> > can be restarted, which could be argued to be a user error. However, that
> > is no reason to let the compiler introduce additional confusion, and to
> > this end, the hrtimer_sleeper_task_get() was introduced, use of which also
> > has the benefit of avoiding open-code access to hrtimer_sleeper innards.
> >
> > KCSAN located this issue.
> >
> > Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
> > Cc: Benjamin LaHaise <bcrl@kvack.org>
> > Cc: Alexander Viro <viro@zeniv.linux.org.uk>
> > Cc: Christian Brauner <brauner@kernel.org>
> > Cc: Jan Kara <jack@suse.cz>
> > Cc: Anna-Maria Behnsen <anna-maria@linutronix.de>
> > Cc: Frederic Weisbecker <frederic@kernel.org>
> > Cc: Thomas Gleixner <tglx@kernel.org>
> > Cc: <linux-aio@kvack.org>
> > Cc: <linux-fsdevel@vger.kernel.org>
> > ---
>
> Reviewed-by: Christian Brauner (Amutable) <brauner@kernel.org>
Thank you both, and I will apply your tags on my next rebase.
Thanx, Paul
next prev parent reply other threads:[~2026-07-31 17:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 0:39 [PATCH RFC 0/9] Fix data races on " Paul E. McKenney
2026-07-31 0:40 ` [PATCH RFC 1/9] hrtimer: Mark data-racy accesses to " Paul E. McKenney
2026-08-04 17:25 ` Dmitry Ilvokhin
2026-08-11 13:35 ` Thomas Gleixner
2026-08-11 19:15 ` Paul E. McKenney
2026-07-31 0:40 ` [PATCH RFC 2/9] aio: Use accessor for " Paul E. McKenney
2026-07-31 12:32 ` Jan Kara
2026-07-31 12:57 ` Christian Brauner
2026-07-31 17:40 ` Paul E. McKenney [this message]
2026-07-31 0:40 ` [PATCH RFC 3/9] wait: " Paul E. McKenney
2026-07-31 0:40 ` [PATCH RFC 4/9] io-uring/rw: " Paul E. McKenney
2026-07-31 15:03 ` Jens Axboe
2026-07-31 17:42 ` Paul E. McKenney
2026-07-31 0:40 ` [PATCH RFC 5/9] futex: Use accessor for hrtimer_sleeper ->task field in waitwake.c Paul E. McKenney
2026-08-03 15:20 ` André Almeida
2026-08-04 17:29 ` Dmitry Ilvokhin
2026-07-31 0:40 ` [PATCH RFC 6/9] timers: Use accessor for hrtimer_sleeper ->task field in sleep_timeout.c Paul E. McKenney
2026-08-04 17:31 ` Dmitry Ilvokhin
2026-07-31 0:40 ` [PATCH RFC 7/9] net: pktgen: Use accessor for hrtimer_sleeper ->task field Paul E. McKenney
2026-07-31 0:40 ` [PATCH RFC 8/9] rtmutex: " Paul E. McKenney
2026-08-04 17:32 ` Dmitry Ilvokhin
2026-08-04 20:15 ` Paul E. McKenney
2026-07-31 0:40 ` [PATCH RFC 9/9] futex: Use accessor for hrtimer_sleeper ->task field in requeue Paul E. McKenney
2026-08-03 15:21 ` André Almeida
2026-08-03 15:45 ` 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=0f8ddd97-89e1-45c8-a779-e56adcde4098@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=bcrl@kvack.org \
--cc=brauner@kernel.org \
--cc=frederic@kernel.org \
--cc=jack@suse.cz \
--cc=kernel-team@meta.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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®