sched: Snapshot thread flags
authorMark Rutland <mark.rutland@arm.com>
Mon, 29 Nov 2021 13:06:45 +0000 (13:06 +0000)
committerThomas Gleixner <tglx@linutronix.de>
Tue, 30 Nov 2021 23:06:43 +0000 (00:06 +0100)
commit0569b245132c40015281610353935a50e282eb94
tree88cb445a3da3d7837dda05ce3ffa8381cc75b1c6
parent6ce895128b3bff738fe8d9dd74747a03e319e466
sched: Snapshot thread flags

Some thread flags can be set remotely, and so even when IRQs are disabled,
the flags can change under our feet. Generally this is unlikely to cause a
problem in practice, but it is somewhat unsound, and KCSAN will
legitimately warn that there is a data race.

To avoid such issues, a snapshot of the flags has to be taken prior to
using them. Some places already use READ_ONCE() for that, others do not.

Convert them all to the new flag accessor helpers.

The READ_ONCE(ti->flags) .. cmpxchg(ti->flags) loop in
set_nr_if_polling() is left as-is for clarity.

Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Paul E. McKenney <paulmck@kernel.org>
Cc: Juri Lelli <juri.lelli@redhat.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>
Link: https://lore.kernel.org/r/20211129130653.2037928-4-mark.rutland@arm.com
kernel/sched/core.c