tree 8390d91f247b724dd00ad91f25d8bcf391e3a52c
parent 668533dc0764b30c9dd2baf3ca800156f688326b
author Linus Torvalds <torvalds@linux-foundation.org> 1511983689 -0800
committer Linus Torvalds <torvalds@linux-foundation.org> 1511983689 -0800

vsprintf: don't use 'restricted_pointer()' when not restricting

Instead, just fall back on the new '%p' behavior which hashes the
pointer.

Otherwise, '%pK' - that was intended to mark a pointer as restricted -
just ends up leaking pointers that a normal '%p' wouldn't leak.  Which
just make the whole thing pointless.

I suspect we should actually get rid of '%pK' entirely, and make it just
work as '%p' regardless, but this is the minimal obvious fix.  People
who actually use 'kptr_restrict' should weigh in on which behavior they
want.

Cc: Tobin Harding <me@tobin.cc>
Cc: Kees Cook <keescook@chromium.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>