From: Mark Rutland <mark.rutland@arm.com>
To: linux-kernel@vger.kernel.org
Cc: boqun.feng@gmail.com, bp@alien8.de, catalin.marinas@arm.com,
dvyukov@google.com, elver@google.com, ink@jurassic.park.msu.ru,
jonas@southpole.se, juri.lelli@redhat.com, linux@armlinux.org.uk,
luto@kernel.org, mark.rutland@arm.com, mattst88@gmail.com,
mingo@redhat.com, monstr@monstr.eu, paulmck@kernel.org,
peterz@infradead.org, rth@twiddle.net, shorne@gmail.com,
stefan.kristiansson@saunalahti.fi, tglx@linutronix.de,
vincent.guittot@linaro.org, will@kernel.org
Subject: [PATCH v2 5/9] arm: snapshot thread flags
Date: Mon, 21 Jun 2021 10:05:57 +0100 [thread overview]
Message-ID: <20210621090602.16883-6-mark.rutland@arm.com> (raw)
In-Reply-To: <20210621090602.16883-1-mark.rutland@arm.com>
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.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Cc: Russell King <linux@armlinux.org.uk>
---
arch/arm/kernel/signal.c | 2 +-
arch/arm/mm/alignment.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/kernel/signal.c b/arch/arm/kernel/signal.c
index a3a38d0a4c85..40c1178bd8c2 100644
--- a/arch/arm/kernel/signal.c
+++ b/arch/arm/kernel/signal.c
@@ -674,7 +674,7 @@ do_work_pending(struct pt_regs *regs, unsigned int thread_flags, int syscall)
}
}
local_irq_disable();
- thread_flags = current_thread_info()->flags;
+ thread_flags = read_thread_flags();
} while (thread_flags & _TIF_WORK_MASK);
return 0;
}
diff --git a/arch/arm/mm/alignment.c b/arch/arm/mm/alignment.c
index ea81e89e7740..adbb3817d0be 100644
--- a/arch/arm/mm/alignment.c
+++ b/arch/arm/mm/alignment.c
@@ -990,7 +990,7 @@ do_alignment(unsigned long addr, unsigned int fsr, struct pt_regs *regs)
* there is no work pending for this thread.
*/
raw_local_irq_disable();
- if (!(current_thread_info()->flags & _TIF_WORK_MASK))
+ if (!(read_thread_flags() & _TIF_WORK_MASK))
set_cr(cr_no_alignment);
}
--
2.11.0
next prev parent reply other threads:[~2021-06-21 9:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 9:05 [PATCH v2 0/9] thread_info: use helpers to " Mark Rutland
2021-06-21 9:05 ` [PATCH v2 1/9] thread_info: add " Mark Rutland
2021-06-21 9:05 ` [PATCH v2 2/9] entry: " Mark Rutland
2021-06-21 9:05 ` [PATCH v2 3/9] sched: " Mark Rutland
2021-06-21 9:05 ` [PATCH v2 4/9] alpha: " Mark Rutland
2021-06-21 9:05 ` Mark Rutland [this message]
2021-06-21 9:05 ` [PATCH v2 6/9] arm64: read " Mark Rutland
2021-06-21 9:05 ` [PATCH v2 6/9] arm64: snapshot " Mark Rutland
2021-06-21 9:06 ` [PATCH v2 7/9] microblaze: " Mark Rutland
2021-06-21 9:06 ` [PATCH v2 8/9] openrisc: " Mark Rutland
2021-06-21 9:06 ` [PATCH v2 9/9] x86: " Mark Rutland
2021-06-21 17:54 ` [PATCH v2 0/9] thread_info: use helpers to " Will Deacon
2021-06-22 14:45 ` Mark Rutland
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=20210621090602.16883-6-mark.rutland@arm.com \
--to=mark.rutland@arm.com \
--cc=boqun.feng@gmail.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=ink@jurassic.park.msu.ru \
--cc=jonas@southpole.se \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=luto@kernel.org \
--cc=mattst88@gmail.com \
--cc=mingo@redhat.com \
--cc=monstr@monstr.eu \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rth@twiddle.net \
--cc=shorne@gmail.com \
--cc=stefan.kristiansson@saunalahti.fi \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=will@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
all inboxes | Powered by JetHome®