Linus Torvalds ef0010a309 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>
2017-11-29 11:28:09 -08:00
..
2017-08-15 09:02:08 -07:00
2015-11-23 09:44:58 +01:00
2017-10-07 10:45:14 -06:00
2017-02-24 17:46:57 -08:00
2017-11-17 16:10:01 -08:00
2014-08-08 15:57:25 -07:00
2016-12-06 10:17:03 +02:00
2015-09-08 14:35:59 -07:00
2017-09-19 15:18:33 -07:00
2016-08-02 17:31:41 -04:00
2017-08-15 09:02:07 -07:00