From: Joe Perches <joe@perches.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
akpm@linux-foundation.org, netdev@vger.kernel.org,
drosenberg@vsecurity.com, a.p.zijlstra@chello.nl,
eparis@parisplace.org, eugeneteo@kernel.org, jmorris@namei.org,
kees.cook@canonical.com, mingo@elte.hu, tgraf@infradead.org
Subject: Re: [patch 1/1] net: convert %p usage to %pK
Date: Mon, 23 May 2011 23:33:13 -0700 [thread overview]
Message-ID: <1306218793.2298.10.camel@Joe-Laptop> (raw)
In-Reply-To: <1306217837.2638.36.camel@edumazet-laptop>
On Tue, 2011-05-24 at 08:17 +0200, Eric Dumazet wrote:
> We probably need to extend this to inet_diag as well.
> Provide a mayber_hide_ptr() helper and use it in inet_diag to not
> disclose kernel pointers to user, with kptr_restrict logic :
> kptr_restrict = 0 : kernel pointers are not mangled
> kptr_restrict = 1 : if the current user does not have CAP_SYSLOG,
> kernel pointers are replaced by 0
> kptr_restrict = 2 : kernel pointers are replaced by 0
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
> diff --git a/lib/vsprintf.c b/lib/vsprintf.c
[]
> +void *maybe_hide_ptr(void *ptr)
> +{
> + if (!((kptr_restrict == 0) ||
> + (kptr_restrict == 1 &&
> + has_capability_noaudit(current, CAP_SYSLOG))))
> + ptr = NULL;
> + return ptr;
> +}
> +EXPORT_SYMBOL(maybe_hide_ptr);
Makes sense to me.
Maybe for clarity it'd be better to use a switch/case
or something like:
if (kptr_restrict == 0)
return ptr;
if (ptr_restrict == 1 &&
has_capability_noaudit(current, CAP_SYSLOG))
return ptr;
return NULL;
next prev parent reply other threads:[~2011-05-24 6:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 22:17 [patch 1/1] net: convert %p usage to %pK akpm
2011-05-24 5:13 ` David Miller
2011-05-24 6:17 ` Eric Dumazet
2011-05-24 6:33 ` Joe Perches [this message]
2011-05-24 6:57 ` Ingo Molnar
2011-05-24 7:04 ` Eric Dumazet
2011-05-24 7:35 ` Joe Perches
2011-05-24 7:45 ` Eric Dumazet
2011-05-24 7:58 ` David Miller
2011-05-24 14:43 ` Stephen Hemminger
2011-05-24 17:18 ` David Miller
2011-05-25 23:29 ` Kees Cook
2011-05-26 1:50 ` David Miller
2011-05-27 0:14 ` Kees Cook
2011-05-27 2:44 ` David Miller
2011-05-27 3:10 ` Eric Dumazet
2011-05-27 6:37 ` Ingo Molnar
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=1306218793.2298.10.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=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).