From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: bigeasy@linutronix.de, linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
John Ogness <john.ogness@linutronix.de>,
Mike Galbraith <efault@gmx.de>, Petr Mladek <pmladek@suse.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Theodore Ts'o <tytso@mit.edu>,
Thomas Gleixner <tglx@linutronix.de>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: [PATCH v4] lib/vsprintf: defer filling siphash key on RT
Date: Mon, 1 Aug 2022 14:39:46 +0200 [thread overview]
Message-ID: <20220801123945.43081-1-Jason@zx2c4.com> (raw)
In-Reply-To: <YufHN7fF0dROMETj@zx2c4.com>
On RT, we can't call get_random_bytes() from inside of the raw locks
that callers of vsprintf might take, because get_random_bytes() takes
normal spinlocks. So on those RT systems, defer the siphash key
generation to a worker.
Also, avoid using a static_branch, as this isn't the fast path.
Using static_branch_likely() to signal that ptr_key has been filled is a
bit much given that it is not a fast path.
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Reported-by: Mike Galbraith <efault@gmx.de>
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
---
Sebastian - feel free to take this and tweak it as needed. Sending this
mostly as something illustrative of what the "simpler" thing would be
that I had in mind. -Jason
lib/vsprintf.c | 35 ++++++++++++++++++++---------------
1 file changed, 20 insertions(+), 15 deletions(-)
diff --git a/lib/vsprintf.c b/lib/vsprintf.c
index 3c1853a9d1c0..5a67f6f65ddc 100644
--- a/lib/vsprintf.c
+++ b/lib/vsprintf.c
@@ -750,37 +750,42 @@ static int __init debug_boot_weak_hash_enable(char *str)
}
early_param("debug_boot_weak_hash", debug_boot_weak_hash_enable);
-static DEFINE_STATIC_KEY_FALSE(filled_random_ptr_key);
+static bool filled_ptr_key __read_mostly;
+static siphash_key_t ptr_key __read_mostly;
-static void enable_ptr_key_workfn(struct work_struct *work)
+static void fill_ptr_key_workfn(struct work_struct *work)
{
- static_branch_enable(&filled_random_ptr_key);
+ if (READ_ONCE(filled_ptr_key))
+ return;
+ get_random_bytes(&ptr_key, sizeof(ptr_key));
+ /* Pairs with smp_rmb() before reading ptr_key. */
+ smp_wmb();
+ WRITE_ONCE(filled_ptr_key, true);
}
/* Maps a pointer to a 32 bit unique identifier. */
static inline int __ptr_to_hashval(const void *ptr, unsigned long *hashval_out)
{
- static siphash_key_t ptr_key __read_mostly;
unsigned long hashval;
- if (!static_branch_likely(&filled_random_ptr_key)) {
- static bool filled = false;
+ if (!READ_ONCE(filled_ptr_key)) {
static DEFINE_SPINLOCK(filling);
- static DECLARE_WORK(enable_ptr_key_work, enable_ptr_key_workfn);
unsigned long flags;
- if (!system_unbound_wq || !rng_is_initialized() ||
- !spin_trylock_irqsave(&filling, flags))
+ if (IS_ENABLED(CONFIG_PREEMPT_RT) && rng_is_initialized()) {
+ static DECLARE_WORK(fill_ptr_key_work, fill_ptr_key_workfn);
+ queue_work(system_unbound_wq, &fill_ptr_key_work);
return -EAGAIN;
-
- if (!filled) {
- get_random_bytes(&ptr_key, sizeof(ptr_key));
- queue_work(system_unbound_wq, &enable_ptr_key_work);
- filled = true;
}
+
+ if (!rng_is_initialized() || !spin_trylock_irqsave(&filling, flags))
+ return -EAGAIN;
+
+ fill_ptr_key_workfn(NULL);
spin_unlock_irqrestore(&filling, flags);
}
-
+ /* Pairs with smp_wmb() after writing ptr_key. */
+ smp_rmb();
#ifdef CONFIG_64BIT
hashval = (unsigned long)siphash_1u64((u64)ptr, &ptr_key);
--
2.35.1
next prev parent reply other threads:[~2022-08-01 12:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 15:47 [PATCH 0/2 v2] Init the hashed pointer from a worker Sebastian Andrzej Siewior
2022-07-29 15:47 ` [PATCH 1/2 v2] lib/vsprintf: Remove static_branch_likely() from __ptr_to_hashval() Sebastian Andrzej Siewior
2022-08-01 12:11 ` Jason A. Donenfeld
2022-08-01 12:41 ` Sebastian Andrzej Siewior
2022-08-01 12:13 ` Jason A. Donenfeld
2022-08-01 12:42 ` Sebastian Andrzej Siewior
2022-07-29 15:47 ` [PATCH 2/2 v2] lib/vsprintf: Initialize vsprintf's pointer hash once the random core is ready Sebastian Andrzej Siewior
2022-07-29 23:29 ` Jason A. Donenfeld
2022-08-01 7:32 ` Sebastian Andrzej Siewior
2022-08-01 9:34 ` [PATCH 2/2 v3] " Sebastian Andrzej Siewior
2022-08-01 12:36 ` Jason A. Donenfeld
2022-08-01 12:39 ` Jason A. Donenfeld [this message]
2022-08-01 12:46 ` [PATCH v4] lib/vsprintf: defer filling siphash key on RT Sebastian Andrzej Siewior
2022-08-01 13:36 ` Jason A. Donenfeld
2022-08-01 13:44 ` Jason A. Donenfeld
2022-08-01 14:25 ` Sebastian Andrzej Siewior
2022-08-01 14:30 ` Jason A. Donenfeld
2022-08-01 13:47 ` Sebastian Andrzej Siewior
2022-08-01 13:55 ` Jason A. Donenfeld
2022-08-01 14:12 ` [PATCH v5] " Jason A. Donenfeld
2022-08-01 14:26 ` Sebastian Andrzej Siewior
2022-08-01 12:41 ` [PATCH 2/2 v3] lib/vsprintf: Initialize vsprintf's pointer hash once the random core is ready Sebastian Andrzej Siewior
2022-09-20 15:01 ` Jason A. Donenfeld
2022-09-23 10:36 ` Petr Mladek
2022-09-23 15:28 ` Sebastian Andrzej Siewior
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=20220801123945.43081-1-Jason@zx2c4.com \
--to=jason@zx2c4.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=efault@gmx.de \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
/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