| Message ID | 1513636145-30033-3-git-send-email-me@tobin.cc (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
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@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..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 >
On Mon, Dec 18, 2017 at 03:50:06PM -0800, Randy Dunlap wrote: > 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 ............ ^^^^^^^^^^^^. Oh thanks. Took quite a few minutes of staring to see the mistake ;) Will fix and re-spin. thanks, Tobin.
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
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(-)