From: "Tobin C. Harding" <me@tobin.cc>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Tobin C. Harding" <me@tobin.cc>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Kees Cook <keescook@chromium.org>,
Alexander Popov <alex.popov@linux.com>,
kernel-hardening@lists.openwall.com
Subject: [PATCH v2 2/3] doc: update kpt_restrict documentation
Date: Mon, 18 Dec 2017 09:30:06 +1100 [thread overview]
Message-ID: <1513549807-20287-3-git-send-email-me@tobin.cc> (raw)
In-Reply-To: <1513549807-20287-1-git-send-email-me@tobin.cc>
Recently the behaviour of printk specifier %pK was changed. The
documentation does not currently mirror this.
Update documentation for sysctl kpt_restrict.
Signed-off-by: Tobin C. Harding <me@tobin.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..6b039aa1427a 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
--
2.7.4
next prev parent reply other threads:[~2017-12-17 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-17 22:30 [PATCH v2 0/3] doc: update printk documentation Tobin C. Harding
2017-12-17 22:30 ` [PATCH v2 1/3] doc: convert printk-formats.txt to rst Tobin C. Harding
2017-12-17 22:30 ` Tobin C. Harding [this message]
2017-12-18 2:48 ` [PATCH v2 2/3] doc: update kpt_restrict documentation Randy Dunlap
2017-12-17 22:30 ` [PATCH v2 3/3] doc: add documentation on printing kernel addresses Tobin C. Harding
2017-12-17 22:34 ` [PATCH v2 0/3] doc: update printk documentation Joe Perches
2017-12-17 23:56 ` Tobin C. Harding
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=1513549807-20287-3-git-send-email-me@tobin.cc \
--to=me@tobin.cc \
--cc=alex.popov@linux.com \
--cc=corbet@lwn.net \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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