[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 12 Jul 2016 15:23:59 -0400
From: Daniel Micay <danielmicay@...il.com>
To: kernel-hardening@...ts.openwall.com, Emese Revfy <re.emese@...il.com>
Cc: PaX Team <pageexec@...email.hu>, Brad Spengler <spender@...ecurity.net>,
Michal Marek <mmarek@...e.com>, LKML <linux-kernel@...r.kernel.org>,
Masahiro Yamada <yamada.masahiro@...ionext.com>, linux-kbuild
<linux-kbuild@...r.kernel.org>, minipli@...linux.so, Russell King
<linux@...linux.org.uk>, Catalin Marinas <catalin.marinas@....com>, Rasmus
Villemoes <linux@...musvillemoes.dk>, David Brown
<david.brown@...aro.org>, "benh@...nel.crashing.org"
<benh@...nel.crashing.org>, Thomas Gleixner <tglx@...utronix.de>, Andrew
Morton <akpm@...ux-foundation.org>, Jeff Layton <jlayton@...chiereds.net>,
Arnd Bergmann <arnd@...db.de>, Sam Ravnborg <sam@...nborg.org>, Karsten
Keil <isdn@...ux-pingi.de>
Subject: Re: Re: [PATCH v2 2/3] Mark functions with the
__nocapture attribute
On Tue, 2016-07-12 at 15:08 -0400, Kees Cook wrote:
> On Mon, Jul 4, 2016 at 7:42 PM, Emese Revfy <re.emese@...il.com>
> wrote:
> >
> > The nocapture gcc attribute can be on functions only.
> > The attribute takes one or more unsigned integer constants as
> > parameters
> > that specify the function argument(s) of const char* type to
> > initify.
> > If the marked argument is a vararg then the plugin initifies
> > all vararg arguments.
>
> Why is this called "nocapture"? Not captured by what? It seems like
> it
> means "initify this if possible". Am I misunderstanding its purpose?
It means they don't escape via that function, i.e. they aren't stored
anywhere to be used in any way after the call.
Download attachment "signature.asc" of type "application/pgp-signature" (852 bytes)
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.
