[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1513549807-20287-3-git-send-email-me@tobin.cc>
Date: Mon, 18 Dec 2017 09:30:06 +1100
From: "Tobin C. Harding" <me@...in.cc>
To: Jonathan Corbet <corbet@....net>
Cc: "Tobin C. Harding" <me@...in.cc>,
Randy Dunlap <rdunlap@...radead.org>,
linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org,
Kees Cook <keescook@...omium.org>,
Alexander Popov <alex.popov@...ux.com>,
kernel-hardening@...ts.openwall.com
Subject: [PATCH v2 2/3] doc: update kpt_restrict documentation
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@...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..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
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.
