Re: [PATCH v4] kptr_restrict for hiding kernel pointers

[Eric Dumazet]

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.

At least, if a mission critical legacy app want to see real pointers
values and a 2.6.38 kernel, it is a matter of sysadmin tweaks.



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/