From: "Tobin C. Harding" <me@tobin.cc>
To: linux-kernel@vger.kernel.org
Cc: "Tobin C. Harding" <me@tobin.cc>,
Linus Torvalds <torvalds@linux-foundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Kees Cook <keescook@chromium.org>,
Anna-Maria Gleixner <anna-maria@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: [PATCH 3/3] vsprintf: Add use-early-random-bytes cmd line option
Date: Wed, 2 May 2018 09:33:40 +1000 [thread overview]
Message-ID: <1525217620-4107-4-git-send-email-me@tobin.cc> (raw)
In-Reply-To: <1525217620-4107-1-git-send-email-me@tobin.cc>
Currently if an attempt is made to print a pointer before there is
enough entropy then '(____ptrval____)' is printed. This makes debugging
early stage stack traces difficult. We can relax the requirement for
cryptographically secure hashing when debugging while still maintaining
pointer hashing behaviour.
Add a command line option 'use-early-random-bytes'. When enabled get
key material from the hw RNG if available.
This option should NOT be enabled on production kernels.
Suggested-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Tobin C. Harding <me@tobin.cc>
---
lib/vsprintf.c | 50 +++++++++++++++++++++++++++++++++++++++++++++++---
1 file changed, 47 insertions(+), 3 deletions(-)
diff --git a/lib/vsprintf.c b/lib/vsprintf.c
index b82f0c6c2aec..7b9cf6bb9fd2 100644
--- a/lib/vsprintf.c
+++ b/lib/vsprintf.c
@@ -1654,12 +1654,39 @@ char *device_node_string(char *buf, char *end, struct device_node *dn,
return widen_string(buf, buf - buf_start, end, spec);
}
+/*
+ * Command line option use_early_random_bytes allows debugging early in
+ * the boot sequence, if enabled we attempt to use the hw RNG to get
+ * ptr_key material. Do NOT use on production kernels.
+ */
+static int use_early_random_bytes;
+EXPORT_SYMBOL(use_early_random_bytes);
+
+/*
+ * Process kernel command-line parameter at boot time.
+ * use_early_random_bytes=0 or use_early_random_bytes=1
+ */
+static int __init use_early_random_bytes_enable(char *str)
+{
+ long option;
+ int ret;
+
+ ret = !!kstrtol(str, 10, &option);
+ if (ret == 0 && option != 0)
+ use_early_random_bytes = 1;
+
+ pr_info("use_early_random_bytes: %s\n",
+ use_early_random_bytes ? "enabled" : "disabled");
+
+ return 1;
+}
+__setup("use-early-random-bytes=", use_early_random_bytes_enable);
+
static bool have_filled_random_ptr_key __read_mostly;
static siphash_key_t ptr_key __read_mostly;
-static void fill_random_ptr_key(struct random_ready_callback *unused)
+static void ptr_key_ready(void)
{
- get_random_bytes(&ptr_key, sizeof(ptr_key));
/*
* have_filled_random_ptr_key==true is dependent on get_random_bytes().
* ptr_to_id() needs to see have_filled_random_ptr_key==true
@@ -1669,13 +1696,30 @@ static void fill_random_ptr_key(struct random_ready_callback *unused)
WRITE_ONCE(have_filled_random_ptr_key, true);
}
+static void fill_random_ptr_key(struct random_ready_callback *unused)
+{
+ get_random_bytes(&ptr_key, sizeof(ptr_key));
+ ptr_key_ready();
+}
+
static struct random_ready_callback random_ready = {
.func = fill_random_ptr_key
};
static int __init initialize_ptr_random(void)
{
- int ret = add_random_ready_callback(&random_ready);
+ int ret;
+
+ if (use_early_random_bytes) {
+ int nbytes = sizeof(ptr_key);
+
+ if (get_random_bytes_arch(&ptr_key, nbytes) == nbytes) {
+ ptr_key_ready();
+ return 0;
+ }
+ }
+
+ ret = add_random_ready_callback(&random_ready);
if (!ret) {
return 0;
--
2.7.4
next prev parent reply other threads:[~2018-05-01 23:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 23:33 [PATCH 0/3] enable early printing of hashed pointers Tobin C. Harding
2018-05-01 23:33 ` [PATCH 1/3] random: Fix whitespace pre random-bytes work Tobin C. Harding
2018-05-02 0:18 ` Theodore Y. Ts'o
2018-05-01 23:33 ` [PATCH 2/3] random: Return nbytes filled from hw RNG Tobin C. Harding
2018-05-01 23:44 ` Tobin C. Harding
2018-05-02 0:19 ` Theodore Y. Ts'o
2018-05-02 1:39 ` Steven Rostedt
2018-05-02 2:07 ` Tobin C. Harding
2018-05-01 23:33 ` Tobin C. Harding [this message]
2018-05-02 1:02 ` [PATCH 3/3] vsprintf: Add use-early-random-bytes cmd line option Linus Torvalds
2018-05-02 1:27 ` tcharding
2018-05-02 1:45 ` Steven Rostedt
2018-05-02 2:05 ` tcharding
2018-05-02 2:51 ` Linus Torvalds
2018-05-02 21:56 ` Andrew Morton
2018-05-03 2:56 ` Tobin C. Harding
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=1525217620-4107-4-git-send-email-me@tobin.cc \
--to=me@tobin.cc \
--cc=akpm@linux-foundation.org \
--cc=anna-maria@linutronix.de \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
--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
Powered by JetHome