On Wed, Dec 13, 2017 at 4:59 AM, Michael Ellerman wrote:
>
> Right. My email was only about the kptr_restrict = 1 case, but I didn't
> actually make that clear.
>
> But that's also sort of my point, it has multiple modes of operation,
> which is useful.
No it isn't.
It's completely useless. Let
Linus Torvalds writes:
> This is a perfect example of just %pK being complete shit.
>
> %pK doesn't actually do any file permissions right. It looks like it does
> it, but it's just a hot mess of garbage.
>
> And %pK doesn't even work the way you claim it does. Not in the general
> case, and only
On Mon, Dec 11, 2017 at 11:59:30AM -0800, Kees Cook wrote:
> On Sun, Dec 10, 2017 at 1:47 PM, Paul E. McKenney
> wrote:
> > On Sun, Dec 10, 2017 at 12:39:11PM -0800, Linus Torvalds wrote:
> >> I'd rather make %pK act more like %p than have gratuitous differences.
>
> The feature that paranoid fol
On Sun, Dec 10, 2017 at 1:47 PM, Paul E. McKenney
wrote:
> On Sun, Dec 10, 2017 at 12:39:11PM -0800, Linus Torvalds wrote:
>> I'd rather make %pK act more like %p than have gratuitous differences.
The feature that paranoid folks currently depend on is getting a value
entirely zeroed out with %pK
On Sun, Dec 10, 2017 at 12:39:11PM -0800, Linus Torvalds wrote:
> On Sun, Dec 10, 2017 at 4:52 AM, Andy Shevchenko
> wrote:
> >>
> >>> Perhaps it should have printed a fixed, non-zero value for non-zero
> >>> pointers.
> >>
> >> I must leave this to the people who have a dog in that contest. ;-)
On Sun, Dec 10, 2017 at 4:52 AM, Andy Shevchenko
wrote:
>>
>>> Perhaps it should have printed a fixed, non-zero value for non-zero
>>> pointers.
>>
>> I must leave this to the people who have a dog in that contest. ;-)
>
> Since there is an ongoing discussion with security people near to %pK
> an
On Sun, Dec 10, 2017 at 02:52:49PM +0200, Andy Shevchenko wrote:
> On Mon, Dec 4, 2017 at 6:11 PM, Paul E. McKenney
> wrote:
> > On Mon, Dec 04, 2017 at 02:13:38PM +, David Laight wrote:
> >> From: Paul E. McKenney
> >> > Sent: 04 December 2017 13:42
> >> > On Mon, Dec 04, 2017 at 12:32:30PM +
On Mon, Dec 4, 2017 at 6:11 PM, Paul E. McKenney
wrote:
> On Mon, Dec 04, 2017 at 02:13:38PM +, David Laight wrote:
>> From: Paul E. McKenney
>> > Sent: 04 December 2017 13:42
>> > On Mon, Dec 04, 2017 at 12:32:30PM +, David Laight wrote:
>> > > From: Paul E. McKenney
>> > > > Sent: 01 Dec
On Mon, Dec 04, 2017 at 02:13:38PM +, David Laight wrote:
> From: Paul E. McKenney
> > Sent: 04 December 2017 13:42
> > On Mon, Dec 04, 2017 at 12:32:30PM +, David Laight wrote:
> > > From: Paul E. McKenney
> > > > Sent: 01 December 2017 20:09
> > > >
> > > > Because %p prints "(null)" and
From: Paul E. McKenney
> Sent: 04 December 2017 13:42
> On Mon, Dec 04, 2017 at 12:32:30PM +, David Laight wrote:
> > From: Paul E. McKenney
> > > Sent: 01 December 2017 20:09
> > >
> > > Because %p prints "(null)" and %pK prints "" or (on
> > > 32-bit systems) "", this
On Mon, Dec 04, 2017 at 12:32:30PM +, David Laight wrote:
> From: Paul E. McKenney
> > Sent: 01 December 2017 20:09
> >
> > Because %p prints "(null)" and %pK prints "" or (on
> > 32-bit systems) "", this commit adjusts torture-test scripting
> > accordingly.
>
> Surel
From: Paul E. McKenney
> Sent: 01 December 2017 20:09
>
> Because %p prints "(null)" and %pK prints "" or (on
> 32-bit systems) "", this commit adjusts torture-test scripting
> accordingly.
Surely NULL v not-NULL is one bit of info that the message needs to contain?
12 matches
Mail list logo