From: Joe Perches <joe@perches.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, 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, tgraf@infradead.org
Subject: Re: [patch 1/1] net: convert %p usage to %pK
Date: Tue, 24 May 2011 00:35:07 -0700 [thread overview]
Message-ID: <1306222507.2298.23.camel@Joe-Laptop> (raw)
In-Reply-To: <1306220681.2638.40.camel@edumazet-laptop>
On Tue, 2011-05-24 at 09:04 +0200, Eric Dumazet wrote:
> Le mardi 24 mai 2011 à 08:57 +0200, Ingo Molnar a écrit :
> > * Joe Perches <joe@perches.com> wrote:
> > > Maybe for clarity it'd be better to use a switch/case
> > > or something like:
> Here we are, thanks.
Hey Eric. Just more trivia:
> [PATCH v2] inet_diag: hide socket pointers
> Provide a mayber_hide_ptr() helper and use it in inet_diag to not
typo maybe_hide_ptr
> diff --git a/lib/vsprintf.c b/lib/vsprintf.c
> @@ -798,6 +798,26 @@ char *uuid_string(char *buf, char *end, const u8 *addr,
> }
>
> int kptr_restrict __read_mostly;
> +/**
> + * maybe_hide_ptr - Eventually nullify a kernel pointer given to user
Not a great description.
Maybe something like:
* maybe_hide_ptr - Set user values of kernel pointers to null
* when appropriate
[]
> diff --git a/net/ipv4/inet_diag.c b/net/ipv4/inet_diag.c
> index 6ffe94c..b5646a3 100644
> --- a/net/ipv4/inet_diag.c
> +++ b/net/ipv4/inet_diag.c
> @@ -84,6 +84,7 @@ static int inet_csk_diag_fill(struct sock *sk,
> struct inet_diag_meminfo *minfo = NULL;
> unsigned char *b = skb_tail_pointer(skb);
> const struct inet_diag_handler *handler;
> + u64 ptr;
>
> handler = inet_diag_table[unlh->nlmsg_type];
> BUG_ON(handler == NULL);
> @@ -114,8 +115,9 @@ static int inet_csk_diag_fill(struct sock *sk,
> r->idiag_retrans = 0;
>
> r->id.idiag_if = sk->sk_bound_dev_if;
> - r->id.idiag_cookie[0] = (u32)(unsigned long)sk;
> - r->id.idiag_cookie[1] = (u32)(((unsigned long)sk >> 31) >> 1);
> + ptr = (u64)maybe_hide_ptr(sk);
> + r->id.idiag_cookie[0] = (u32)ptr;
> + r->id.idiag_cookie[1] = (u32)(ptr >> 32);
I think it's be better without the casts
using the standard kernel.h macros.
void *ptr;
ptr = maybe_hide_ptr(sk);
r->id.idiag_cookie[0] = lower_32_bits(ptr);
r->id.idiag_cookie[1] = upper_32_bits(ptr);
next prev parent reply other threads:[~2011-05-24 7:35 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
2011-05-24 6:57 ` Ingo Molnar
2011-05-24 7:04 ` Eric Dumazet
2011-05-24 7:35 ` Joe Perches [this message]
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=1306222507.2298.23.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 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.