From: Josh Poimboeuf <jpoimboe@kernel.org>
To: Valentin Schneider <vschneid@redhat.com>
Cc: linux-kernel@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>
Subject: [PATCH v2 1/3] jump_label: Add annotations for validating noinstr usage
Date: Tue, 26 Nov 2024 20:47:40 -0800 [thread overview]
Message-ID: <f9d71d6c6f87b6ea88b904f328595b7663e6a6d2.1732682344.git.jpoimboe@kernel.org> (raw)
In-Reply-To: <cover.1732682344.git.jpoimboe@kernel.org>
Deferring a code patching IPI is unsafe if the patched code is in a
noinstr region. In that case the text poke code must trigger an
immediate IPI to all CPUs, which can rudely interrupt an isolated NO_HZ
CPU running in userspace.
Some noinstr static branches may really need to be patched at runtime,
despite the resulting disruption. Add DEFINE_STATIC_KEY_*_NOINSTR()
variants for those. They don't do anything special yet; that will come
later.
Signed-off-by: Josh Poimboeuf <jpoimboe@kernel.org>
---
include/linux/jump_label.h | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/include/linux/jump_label.h b/include/linux/jump_label.h
index f5a2727ca4a9..88bb6e32fdcb 100644
--- a/include/linux/jump_label.h
+++ b/include/linux/jump_label.h
@@ -385,6 +385,23 @@ struct static_key_false {
#define DEFINE_STATIC_KEY_FALSE_RO(name) \
struct static_key_false name __ro_after_init = STATIC_KEY_FALSE_INIT
+/*
+ * The _NOINSTR variants are used to tell objtool the static key is allowed to
+ * be used in noinstr code.
+ *
+ * They should almost never be used, as they prevent code patching IPIs from
+ * being deferred, which can be problematic for isolated NOHZ_FULL CPUs running
+ * in pure userspace.
+ *
+ * If using one of these _NOINSTR variants, please add a comment above the
+ * definition with the rationale.
+ */
+#define DEFINE_STATIC_KEY_TRUE_NOINSTR(name) \
+ DEFINE_STATIC_KEY_TRUE(name)
+
+#define DEFINE_STATIC_KEY_FALSE_NOINSTR(name) \
+ DEFINE_STATIC_KEY_FALSE(name)
+
#define DECLARE_STATIC_KEY_FALSE(name) \
extern struct static_key_false name
--
2.47.0
next prev parent reply other threads:[~2024-11-27 4:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 4:47 [PATCH v2 0/3] objtool: noinstr validation for static branches/calls Josh Poimboeuf
2024-11-27 4:47 ` Josh Poimboeuf [this message]
2024-11-27 4:47 ` [PATCH v2 2/3] static_call: Add read-only-after-init static calls Josh Poimboeuf
2024-11-27 4:47 ` [PATCH v2 3/3] objtool: Add noinstr validation for static branches/calls Josh Poimboeuf
2024-12-03 12:02 ` Valentin Schneider
2024-12-13 6:21 ` Josh Poimboeuf
2024-11-27 9:38 ` [PATCH v2 0/3] objtool: " Valentin Schneider
2024-11-28 1:35 ` Josh Poimboeuf
2024-12-03 12:00 ` Valentin Schneider
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=f9d71d6c6f87b6ea88b904f328595b7663e6a6d2.1732682344.git.jpoimboe@kernel.org \
--to=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=vschneid@redhat.com \
/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®