From: Andrew Morton <akpm@linux-foundation.org>
To: Joe Perches <joe@perches.com>
Cc: Dan Rosenberg <drosenberg@vsecurity.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vsprintf: Neaten %pK kptr_restrict, save a bit of code space
Date: Wed, 19 Jan 2011 14:50:24 -0800 [thread overview]
Message-ID: <20110119145024.353ef8a1.akpm@linux-foundation.org> (raw)
In-Reply-To: <1294950072.4114.172.camel@Joe-Laptop>
On Thu, 13 Jan 2011 12:21:12 -0800
Joe Perches <joe@perches.com> wrote:
> If kptr restrictions are on, just set the passed pointer to NULL.
>
> $ size lib/vsprintf.o.*
> text data bss dec hex filename
> 8247 4 2 8253 203d lib/vsprintf.o.new
> 8282 4 2 8288 2060 lib/vsprintf.o.old
>
> Signed-off-by: Joe Perches <joe@perches.com>
>
> ---
>
> lib/vsprintf.c | 14 +++++---------
> 1 files changed, 5 insertions(+), 9 deletions(-)
>
> diff --git a/lib/vsprintf.c b/lib/vsprintf.c
> index d3023df..070d134 100644
> --- a/lib/vsprintf.c
> +++ b/lib/vsprintf.c
> @@ -1047,16 +1047,12 @@ char *pointer(const char *fmt, char *buf, char *end, void *ptr,
> 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);
> + if (!((kptr_restrict == 0) ||
> + (kptr_restrict == 1 &&
> + has_capability_noaudit(current, CAP_SYSLOG))))
> + ptr = NULL;
> + break;
> }
> spec.flags |= SMALL;
> if (spec.field_width == -1) {
This hurts my brain. Does it work?
next prev parent reply other threads:[~2011-01-19 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 20:21 [PATCH] vsprintf: Neaten %pK kptr_restrict, save a bit of code space Joe Perches
2011-01-19 22:50 ` Andrew Morton [this message]
2011-01-19 23:11 ` Joe Perches
2011-01-19 23:16 ` Andrew Morton
2011-01-19 23:32 ` Joe Perches
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=20110119145024.353ef8a1.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=drosenberg@vsecurity.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.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