From: Joe Perches <joe@perches.com> To: Greg KH <gregkh@linuxfoundation.org>, kernel-hardening@lists.openwall.com, Petr Mladek <pmladek@suse.com>, Sergey Senozhatsky <sergey.senozhatsky@gmail.com> Cc: linux-kernel@vger.kernel.org, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will.deacon@arm.com>, Steven Rostedt <rostedt@goodmis.org>, William Roberts <william.c.roberts@intel.com>, Chris Fries <cfries@google.com>, Dave Weinstein <olorin@google.com> Subject: Re: [RFC 5/6] lib: vsprintf: Add "%paP", "%padP" options Date: Fri, 05 May 2017 21:42:40 -0700 [thread overview] Message-ID: <1494045760.31950.21.camel@perches.com> (raw) In-Reply-To: <20170506040747.GF32707@kroah.com> On Fri, 2017-05-05 at 21:07 -0700, Greg KH wrote: > From: Chris Fries <cfries@google.com> > > Add %paP and %padP for physical address that need to always be shown > regardless of kptr restrictions. The commit message could be improved. I had to look at the actual code to see if %papP was supported. > diff --git a/Documentation/printk-formats.txt b/Documentation/printk-formats.txt [] > @@ -82,18 +82,20 @@ Struct Resources: > > Physical addresses types phys_addr_t: > > - %pa[p] 0x01234567 or 0x0123456789abcdef > + %pa[p][P] 0x01234567 or 0x0123456789abcdef Well, that's good. > diff --git a/lib/vsprintf.c b/lib/vsprintf.c [] > @@ -1394,23 +1394,29 @@ static noinline_for_stack > char *address_val(char *buf, char *end, const void *addr, const char *fmt) > { > unsigned long long num; > + int cleanse = kptr_restrict_cleanse_addresses(); bool
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com> To: Greg KH <gregkh@linuxfoundation.org>, kernel-hardening@lists.openwall.com, Petr Mladek <pmladek@suse.com>, Sergey Senozhatsky <sergey.senozhatsky@gmail.com> Cc: linux-kernel@vger.kernel.org, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will.deacon@arm.com>, Steven Rostedt <rostedt@goodmis.org>, William Roberts <william.c.roberts@intel.com>, Chris Fries <cfries@google.com>, Dave Weinstein <olorin@google.com> Subject: [kernel-hardening] Re: [RFC 5/6] lib: vsprintf: Add "%paP", "%padP" options Date: Fri, 05 May 2017 21:42:40 -0700 [thread overview] Message-ID: <1494045760.31950.21.camel@perches.com> (raw) In-Reply-To: <20170506040747.GF32707@kroah.com> On Fri, 2017-05-05 at 21:07 -0700, Greg KH wrote: > From: Chris Fries <cfries@google.com> > > Add %paP and %padP for physical address that need to always be shown > regardless of kptr restrictions. The commit message could be improved. I had to look at the actual code to see if %papP was supported. > diff --git a/Documentation/printk-formats.txt b/Documentation/printk-formats.txt [] > @@ -82,18 +82,20 @@ Struct Resources: > > Physical addresses types phys_addr_t: > > - %pa[p] 0x01234567 or 0x0123456789abcdef > + %pa[p][P] 0x01234567 or 0x0123456789abcdef Well, that's good. > diff --git a/lib/vsprintf.c b/lib/vsprintf.c [] > @@ -1394,23 +1394,29 @@ static noinline_for_stack > char *address_val(char *buf, char *end, const void *addr, const char *fmt) > { > unsigned long long num; > + int cleanse = kptr_restrict_cleanse_addresses(); bool
next prev parent reply other threads:[~2017-05-06 4:42 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-05-06 4:06 [RFC 00/06] printk: add more new kernel pointer filter options Greg KH 2017-05-06 4:06 ` [kernel-hardening] " Greg KH 2017-05-06 4:06 ` [RFC 1/6] lib: vsprintf: additional kernel pointer filtering options Greg KH 2017-05-06 4:06 ` [kernel-hardening] " Greg KH 2017-05-16 11:58 ` Petr Mladek 2017-05-16 11:58 ` [kernel-hardening] " Petr Mladek 2017-05-18 14:12 ` Greg KH 2017-05-18 14:12 ` [kernel-hardening] " Greg KH 2017-05-06 4:07 ` [RFC 2/6] lib: vsprintf: whitelist stack traces Greg KH 2017-05-06 4:07 ` [kernel-hardening] " Greg KH 2017-05-06 4:07 ` [RFC 3/6] lib: vsprintf: physical address kernel pointer filtering options Greg KH 2017-05-06 4:07 ` [kernel-hardening] " Greg KH 2017-05-06 10:48 ` Ian Campbell 2017-05-06 4:07 ` [RFC 4/6] lib: vsprintf: default kptr_restrict to the maximum value Greg KH 2017-05-06 4:07 ` [kernel-hardening] " Greg KH 2017-05-06 4:07 ` [RFC 5/6] lib: vsprintf: Add "%paP", "%padP" options Greg KH 2017-05-06 4:07 ` [kernel-hardening] " Greg KH 2017-05-06 4:42 ` Joe Perches [this message] 2017-05-06 4:42 ` [kernel-hardening] " Joe Perches 2017-05-06 5:00 ` Greg KH 2017-05-06 5:00 ` [kernel-hardening] " Greg KH 2017-05-16 14:41 ` Petr Mladek 2017-05-16 14:41 ` [kernel-hardening] " Petr Mladek 2017-05-18 14:12 ` Greg KH 2017-05-18 14:12 ` [kernel-hardening] " Greg KH 2017-05-06 4:07 ` [RFC 6/6] drivers: uio: Un-restrict sysfs pointers for UIO Greg KH 2017-05-06 4:07 ` [kernel-hardening] " Greg KH 2017-05-11 1:37 ` [RFC 00/06] printk: add more new kernel pointer filter options Sergey Senozhatsky 2017-05-11 1:37 ` [kernel-hardening] " Sergey Senozhatsky 2017-05-16 21:36 ` Roberts, William C 2017-05-16 21:36 ` [kernel-hardening] " Roberts, William C 2017-05-18 14:13 ` Greg KH 2017-05-18 14:13 ` [kernel-hardening] " Greg KH 2017-05-19 20:25 ` Roberts, William C 2017-05-19 20:25 ` [kernel-hardening] " Roberts, William C
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=1494045760.31950.21.camel@perches.com \ --to=joe@perches.com \ --cc=catalin.marinas@arm.com \ --cc=cfries@google.com \ --cc=gregkh@linuxfoundation.org \ --cc=kernel-hardening@lists.openwall.com \ --cc=linux-kernel@vger.kernel.org \ --cc=olorin@google.com \ --cc=pmladek@suse.com \ --cc=rostedt@goodmis.org \ --cc=sergey.senozhatsky@gmail.com \ --cc=will.deacon@arm.com \ --cc=william.c.roberts@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.