[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 18 Dec 2017 15:50:06 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: "Tobin C. Harding" <me@...in.cc>, Jonathan Corbet <corbet@....net>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
Kees Cook <keescook@...omium.org>, Alexander Popov <alex.popov@...ux.com>,
Joe Perches <joe@...ches.com>, kernel-hardening@...ts.openwall.com
Subject: Re: [PATCH v3 2/3] doc: update kpt_restrict documentation
On 12/18/2017 02:29 PM, Tobin C. Harding wrote:
> Recently the behaviour of printk specifier %pK was changed. The
> documentation does not currently mirror this.
>
> Update documentation for sysctl kpt_restrict.
Fix subject and here ............ ^^^^^^^^^^^^.
>
> Signed-off-by: Tobin C. Harding <me@...in.cc>
> ---
> Documentation/sysctl/kernel.txt | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/sysctl/kernel.txt b/Documentation/sysctl/kernel.txt
> index 63663039acb7..412314eebda6 100644
> --- a/Documentation/sysctl/kernel.txt
> +++ b/Documentation/sysctl/kernel.txt
> @@ -391,7 +391,8 @@ kptr_restrict:
> This toggle indicates whether restrictions are placed on
> exposing kernel addresses via /proc and other interfaces.
>
> -When kptr_restrict is set to (0), the default, there are no restrictions.
> +When kptr_restrict is set to 0 (the default) the address is hashed before
> +printing. (This is the equivalent to %p.)
>
> When kptr_restrict is set to (1), kernel pointers printed using the %pK
> format specifier will be replaced with 0's unless the user has CAP_SYSLOG
>
--
~Randy
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
