All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Dan Rosenberg <drosenberg@vsecurity.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linux-security-module@vger.kernel.org, jmorris@namei.org,
	tgraf@infradead.org, eugeneteo@kernel.org,
	kees.cook@canonical.com, davem@davemloft.net,
	a.p.zijlstra@chello.nl, akpm@linux-foundation.org,
	eparis@parisplace.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v4] kptr_restrict for hiding kernel pointers
Date: Wed, 22 Dec 2010 17:21:18 +0100	[thread overview]
Message-ID: <20101222162118.GC20358@elte.hu> (raw)
In-Reply-To: <1293025688.3027.82.camel@edumazet-laptop>


* Eric Dumazet <eric.dumazet@gmail.com> wrote:

> Le mercredi 22 décembre 2010 à 08:13 -0500, Dan Rosenberg a écrit :
> > > Hm, why is it off by default? Is there some user-space regression that is caused by 
> > > this?
> > > 
> > > We really want good security measures to be active by default (and to work by 
> > > default) - they are not worth much if they are not.
> > > 
> > 
> > I agree entirely, but I've received a lot of resistance to these types
> > of changes in net.  I'm afraid that if it's enabled by default, no one
> > will actually allow use of the %pK specifier where it should be used.
> > 
> 
> Actually, "net resistance" was against your first patches, using quick
> and dirty techniques (Should I remind you some of them ?)
> 
> Now you have a helper, it should be easier to integrate the changes.

Great - if the concept itself wasnt objected to then i think we should flip the 
default to on.

Thanks,

	Ingo

  reply	other threads:[~2010-12-22 16:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-18 21:41 [PATCH v4] kptr_restrict for hiding kernel pointers Dan Rosenberg
2010-12-22 13:03 ` Ingo Molnar
2010-12-22 13:13   ` Dan Rosenberg
2010-12-22 13:48     ` Eric Dumazet
2010-12-22 13:48       ` Eric Dumazet
2010-12-22 16:21       ` Ingo Molnar [this message]
2010-12-22 20:34         ` Andrew Morton
2010-12-22 16:20     ` 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=20101222162118.GC20358@elte.hu \
    --to=mingo@elte.hu \
    --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=netdev@vger.kernel.org \
    --cc=tgraf@infradead.org \
    --cc=torvalds@linux-foundation.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.