From: Kees Cook <kees.cook@canonical.com>
To: David Miller <davem@davemloft.net>
Cc: eric.dumazet@gmail.com, joe@perches.com, mingo@elte.hu,
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,
tgraf@infradead.org
Subject: Re: [patch 1/1] net: convert %p usage to %pK
Date: Wed, 25 May 2011 16:29:21 -0700 [thread overview]
Message-ID: <20110525232921.GD19633@outflux.net> (raw)
In-Reply-To: <20110524.035801.1555795213632087107.davem@davemloft.net>
Hi David,
On Tue, May 24, 2011 at 03:58:01AM -0400, David Miller wrote:
> From: Eric Dumazet <eric.dumazet@gmail.com>
> Date: Tue, 24 May 2011 09:45:01 +0200
>
> > Le mardi 24 mai 2011 à 00:35 -0700, Joe Perches a écrit :
> >
> >> 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);
> >>
> >
> > I am not sure I want to patch lower_32_bits() and upper_32_bits() for
> > this.
> >
> > They dont work on pointers, but on "numbers", according to kerneldoc
> > Andrew wrote years ago. gcc agrees :
> >
> > net/ipv4/inet_diag.c: In function ‘inet_csk_diag_fill’:
> > net/ipv4/inet_diag.c:119: warning: cast from pointer to integer of different size
> > net/ipv4/inet_diag.c:120: error: invalid operands to binary >>
> > make[1]: *** [net/ipv4/inet_diag.o] Error 1
>
> Also you can't do this, the "cookie" is used by the kernel future
> lookups to find sockets.
>
> The kernel pointer is part of the API, so sorry you can't "hide"
> kernel pointers in this case without really breaking user visible
> things.
But this is precisely what we're trying to control with kptr_restrict.
Setting kptr_restrict will make inet_diag (and some details of similar
things in /proc) meaningless. Based on the name, "diag" isn't going to be
used in normal operation, and kptr_restrict is 0 by default, so only system
owners interested in this will enable it and effectively disable inet_diag.
It seems like everything that fills idiag_cookie needs to be adjusted, not
just the one instance, too:
$ fgrep 'idiag_cookie[0] = ' net/ipv4/inet_diag.c
r->id.idiag_cookie[0] = (u32)(unsigned long)sk;
r->id.idiag_cookie[0] = (u32)(unsigned long)tw;
r->id.idiag_cookie[0] = (u32)(unsigned long)req;
-Kees
--
Kees Cook
Ubuntu Security Team
next prev parent reply other threads:[~2011-05-25 23:32 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
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 [this message]
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=20110525232921.GD19633@outflux.net \
--to=kees.cook@canonical.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=joe@perches.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).