Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 25 Apr 2017 11:05:58 +0200
From: Peter Zijlstra <>
To: Kees Cook <>
Cc: PaX Team <>, LKML <>,
	Eric Biggers <>,
	Christoph Hellwig <>,
	"" <>,
	James Bottomley <>,
	Elena Reshetova <>,
	Hans Liljestrand <>,
	David Windsor <>,
	"" <>, Ingo Molnar <>,
	Arnd Bergmann <>,
	Greg Kroah-Hartman <>,
	Jann Horn <>, "David S. Miller" <>,
	linux-arch <>,
	"" <>
Subject: Re: [PATCH] x86/refcount: Implement fast refcount_t handling

On Mon, Apr 24, 2017 at 03:37:32PM -0700, Kees Cook wrote:
> On Mon, Apr 24, 2017 at 3:01 PM, Peter Zijlstra <> wrote:

> > It does not. It just got free'ed. Nothing will stop the free from
> > happening (or already having happened).
> Well, yes, but that's kind of my point. Detecting inc-from-0 is "too
> late" to offer a protection. It offers notification of a bug, rather
> than stopping an exploit from happening.

Well, your setup (panic_on_warn et al) would have it panic the box. That
will effectively stop the exploit by virtue of stopping everything.

And warn/bug/panic etc.. are I think a better option that silently
letting it happen.

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.