lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 05 Apr 2018 16:04:45 +0300
From:   Andy Shevchenko <>
To:     Petr Mladek <>,
        Linus Torvalds <>
Cc:     Rasmus Villemoes <>,
        "Tobin C . Harding" <>, Joe Perches <>,
        Andrew Morton <>,
        Michal Hocko <>,
        Sergey Senozhatsky <>,
        Steven Rostedt <>,
        Sergey Senozhatsky <>,, Kees Cook <>
Subject: Re: [PATCH v4 2/9] vsprintf: Consistent %pK handling for
 kptr_restrict == 0

On Wed, 2018-04-04 at 10:58 +0200, Petr Mladek wrote:
> restricted_pointer() pretends that it prints the address when
> kptr_restrict
> is set to zero. But it is never called in this situation. Instead,
> pointer() falls back to ptr_to_id() and hashes the pointer.
> This patch removes the potential confusion. klp_restrict is checked
> only
> in restricted_pointer().

>  /* Maps a pointer to a 32 bit unique identifier. */
> -static char *ptr_to_id(char *buf, char *end, void *ptr, struct
> printf_spec spec)
> +static char *ptr_to_id(char *buf, char *end,
> +		       const void *ptr, struct printf_spec spec)

I don't think this change belongs to the patch.

Andy Shevchenko <>
Intel Finland Oy

Powered by blists - more mailing lists