linux-kernel - Re: [PATCH] docs: make kptr_restrict and hash

lists.openwall.net		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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87ldiuyx38.fsf@trenco.lwn.net>
Date: Mon, 22 Dec 2025 15:23:55 -0700
From: Jonathan Corbet <corbet@....net>
To: Marc Herbert <marc.herbert@...ux.intel.com>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, Rick Edgecombe
 <rick.p.edgecombe@...el.com>, Marc Herbert <marc.herbert@...ux.intel.com>
Subject: Re: [PATCH] docs: make kptr_restrict and hash_pointers reference
 each other

Marc Herbert <marc.herbert@...ux.intel.com> writes:

> vsprintf.c uses a mix of the `kernel.kptr_restrict` sysctl and the
> `hash_pointers` boot param to control pointer hashing. But that wasn't
> possible to tell without looking at the source code.
>
> They have a different focus and purpose. To avoid wasting the time of
> users trying to use one instead of the other, simply have them reference
> each other in the Documentation.
>
> Signed-off-by: Marc Herbert <marc.herbert@...ux.intel.com>
> ---
> (please just go ahead with any minor corrections; I mean do not ask
> for my opinion)
> ---
>  Documentation/admin-guide/kernel-parameters.txt | 3 +++
>  Documentation/admin-guide/sysctl/kernel.rst     | 2 ++
>  2 files changed, 5 insertions(+)

This one doesn't apply to docs-next; any chance I could get a respin?

Thanks,

jon