From: Joe Perches <joe@perches.com>
To: Dan Rosenberg <drosenberg@vsecurity.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-security-module@vger.kernel.org, jmorris@namei.org,
eric.dumazet@gmail.com, tgraf@infradead.org,
eugeneteo@kernel.org, kees.cook@canonical.com, mingo@elte.hu,
davem@davemloft.net, a.p.zijlstra@chello.nl,
akpm@linux-foundation.org, eparis@parisplace.org
Subject: Re: [PATCH v7] kptr_restrict for hiding kernel pointers
Date: Wed, 22 Dec 2010 20:10:55 -0800 [thread overview]
Message-ID: <1293077455.28077.6.camel@Joe-Laptop> (raw)
In-Reply-To: <1293069792.9820.342.camel@dan>
On Wed, 2010-12-22 at 21:03 -0500, Dan Rosenberg wrote:
> Add the %pK printk format specifier and
> the /proc/sys/kernel/kptr_restrict sysctl.
Another trivial style comment:
> diff --git a/lib/vsprintf.c b/lib/vsprintf.c
[]
> + case 'K':
> + /*
> + * %pK cannot be used in IRQ context because its test
> + * for CAP_SYSLOG would be meaningless.
> + */
> + if (in_irq() || in_serving_softirq() || in_nmi()) {
> + if (spec.field_width == -1)
> + spec.field_width = 2 * sizeof(void *);
> + return string(buf, end, "pK-error", spec);
> + }
> +
> + else if ((kptr_restrict == 0) ||
> + (kptr_restrict == 1 &&
> + has_capability_noaudit(current, CAP_SYSLOG)))
> + break;
> +
---
> + if (spec.field_width == -1) {
> + spec.field_width = 2 * sizeof(void *);
> + spec.flags |= ZEROPAD;
> + }
> + return number(buf, end, 0, spec);
It'd be slightly smaller code to use:
ptr = 0;
break;
and delete the if block and return number.
> }
> spec.flags |= SMALL;
> if (spec.field_width == -1) {
prev parent reply other threads:[~2010-12-23 4:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 2:03 [PATCH v7] kptr_restrict for hiding kernel pointers Dan Rosenberg
2010-12-23 4:10 ` Joe Perches [this message]
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=1293077455.28077.6.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=drosenberg@vsecurity.com \
--cc=eparis@parisplace.org \
--cc=eric.dumazet@gmail.com \
--cc=eugeneteo@kernel.org \
--cc=jmorris@namei.org \
--cc=kees.cook@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=tgraf@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;
as well as URLs for NNTP newsgroup(s).