tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

docs: make kptr_restrict and hash_pointers reference each other

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@linux.intel.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Message-ID: <20260107-doc-hash-ptr-v2-1-cb4c161218d7@linux.intel.com>

authored by

Marc Herbert and committed by
Jonathan Corbet d9d25684 653793b8

+6
+3
Documentation/admin-guide/kernel-parameters.txt
··· 1969 1969 param "no_hash_pointers" is an alias for 1970 1970 this mode. 1971 1971 1972 + For controlling hashing dynamically at runtime, 1973 + use the "kernel.kptr_restrict" sysctl instead. 1974 + 1972 1975 hashdist= [KNL,NUMA] Large hashes allocated during boot 1973 1976 are distributed across NUMA nodes. Defaults on 1974 1977 for 64-bit NUMA, off otherwise.
+3
Documentation/admin-guide/sysctl/kernel.rst
··· 591 591 When ``kptr_restrict`` is set to 2, kernel pointers printed using 592 592 %pK will be replaced with 0s regardless of privileges. 593 593 594 + For disabling these security restrictions early at boot time (and once 595 + for all), use the ``hash_pointers`` boot parameter instead. 596 + 594 597 softlockup_sys_info & hardlockup_sys_info 595 598 ========================================= 596 599 A comma separated list of extra system information to be dumped when