From: Jonathan Corbet <corbet@lwn.net>
To: Marc Herbert <marc.herbert@linux.intel.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Marc Herbert <marc.herbert@linux.intel.com>
Subject: Re: [PATCH v2] docs: make kptr_restrict and hash_pointers reference each other
Date: Fri, 16 Jan 2026 11:32:36 -0700 [thread overview]
Message-ID: <875x91o1bv.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260107-doc-hash-ptr-v2-1-cb4c161218d7@linux.intel.com>
Marc Herbert <marc.herbert@linux.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@linux.intel.com>
> ---
> Please just go ahead with any minor correction(s); I mean do not ask
> for my opinion.
>
> Changes in v2:
> - Rebased on today's docs-next/master to fix textual, unrelated conflict
> - Stop using backquotes in kernel-parameters.txt for consistency
> - Link to v1: https://patch.msgid.link/20251205-doc-hash-ptr-v1-1-573966cfa404@linux.intel.com
> ---
> Documentation/admin-guide/kernel-parameters.txt | 3 +++
> Documentation/admin-guide/sysctl/kernel.rst | 3 +++
> 2 files changed, 6 insertions(+)
Applied, thanks.
jon
prev parent reply other threads:[~2026-01-16 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 20:21 [PATCH v2] docs: make kptr_restrict and hash_pointers reference each other Marc Herbert
2026-01-07 22:22 ` Randy Dunlap
2026-01-16 18:32 ` Jonathan Corbet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875x91o1bv.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.herbert@linux.intel.com \
--cc=rick.p.edgecombe@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox