From: Christoph Hellwig <hch@infradead.org>
To: william.c.roberts@intel.com
Cc: kernel-hardening@lists.openwall.com, corbet@lwn.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] printk: introduce kptr_restrict level 3
Date: Thu, 6 Oct 2016 06:31:47 -0700 [thread overview]
Message-ID: <20161006133147.GA20206@infradead.org> (raw)
In-Reply-To: <1475690686-16138-1-git-send-email-william.c.roberts@intel.com>
On Wed, Oct 05, 2016 at 02:04:46PM -0400, william.c.roberts@intel.com wrote:
> From: William Roberts <william.c.roberts@intel.com>
>
> Some out-of-tree modules do not use %pK and just use %p, as it's
> the common C paradigm for printing pointers. Because of this,
> kptr_restrict has no affect on the output and thus, no way to
> contain the kernel address leak.
So what? We a) don't care about out of tree modules and b) you could
just triviall fix them up if you care.
No need to bloat the kernel with crap like this.
next prev parent reply other threads:[~2016-10-06 13:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 18:04 [PATCH] printk: introduce kptr_restrict level 3 william.c.roberts
2016-10-05 19:34 ` Kees Cook
2016-10-06 13:17 ` Roberts, William C
2016-10-05 20:52 ` Rasmus Villemoes
2016-10-06 13:23 ` Roberts, William C
2016-10-06 13:31 ` Christoph Hellwig [this message]
2016-10-06 13:47 ` Roberts, William C
2016-10-06 13:56 ` Christoph Hellwig
2016-10-06 14:59 ` Roberts, William C
2016-10-06 21:00 ` Kees Cook
2016-10-06 21:19 ` Joe Perches
2016-10-06 21:25 ` Kees Cook
2016-10-07 14:21 ` Roberts, William C
2016-10-06 14:05 ` [kernel-hardening] " Jann Horn
2016-10-06 14:46 ` Jann Horn
2016-10-07 11:52 ` Jann Horn
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=20161006133147.GA20206@infradead.org \
--to=hch@infradead.org \
--cc=corbet@lwn.net \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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: 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