From: Steven Rostedt <rostedt@goodmis.org>
To: "Tobin C. Harding" <me@tobin.cc>
Cc: Kees Cook <keescook@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Laight <David.Laight@aculab.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Petr Mladek <pmladek@suse.com>
Subject: Re: [RFC][PATCH] tracing, printk: Force no hashing when trace_printk() is used
Date: Tue, 3 Apr 2018 18:59:37 -0400 [thread overview]
Message-ID: <20180403185937.5bcc66de@gandalf.local.home> (raw)
In-Reply-To: <20180403214349.GF781@eros>
On Wed, 4 Apr 2018 07:43:49 +1000
"Tobin C. Harding" <me@tobin.cc> wrote:
> > static noinline_for_stack
> > char *restricted_pointer(char *buf, char *end, const void *ptr,
> > @@ -1962,6 +1963,10 @@ char *pointer(const char *fmt, char *buf, char *end, void *ptr,
> > return pointer_string(buf, end, ptr, spec);
> > }
> >
> > + /* When the kernel is in debugging mode, show all pointers */
> > + if (static_key_false(&trace_debug))
> > + return restricted_pointer(buf, end, ptr, spec);
> > +
> > /* default is to _not_ leak addresses, hash before printing */
> > return ptr_to_id(buf, end, ptr, spec);
> > }
>
> This uses the deprecated API Steve (I only know because I went to read
> Documentation/static-keys.txt after seeing this patch).
Hmm, I've been involved with static keys since it was introduced. I
simply copied the code for the original use case (tracepoints). I
forgot that we are changing the name (this has been an ongoing bikeshed
for some time, I can't keep up. Better than the original suggestion
"really_unlikely()" ;)
I need to update tracepoints too.
-- Steve
next prev parent reply other threads:[~2018-04-03 22:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 19:41 Steven Rostedt
2018-04-03 20:07 ` Kees Cook
2018-04-03 21:06 ` Steven Rostedt
2018-04-03 21:43 ` Tobin C. Harding
2018-04-03 22:59 ` Steven Rostedt [this message]
2018-04-04 7:49 ` Peter Zijlstra
2018-04-04 13:36 ` Steven Rostedt
2018-04-04 16:27 ` Kees Cook
2018-04-04 16:52 ` Steven Rostedt
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=20180403185937.5bcc66de@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=David.Laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@tobin.cc \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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®