[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56414766.18876.2B8A87D7@pageexec.freemail.hu>
Date: Tue, 10 Nov 2015 02:24:54 +0100
From: "PaX Team" <pageexec@...email.hu>
To: Julia Lawall <julia.lawall@...6.fr>, Kees Cook <keescook@...omium.org>
CC: Emese Revfy <re.emese@...il.com>,
"kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>,
Dan Carpenter <dan.carpenter@...cle.com>,
Joe Perches <joe@...ches.com>, kernel-janitors@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: Re: [PATCH] video: constify geode ops structures
> On Mon, Nov 9, 2015 at 1:55 PM, Julia Lawall <julia.lawall@...6.fr> wrote:
> >> > What happens if some structures cannot be made const because there is a
> >> > reassignment somewhere? Is there any feedback about the problem?
the constify plugin basically simulates what a source level 'const' would
do (sets a specific flag on the 'tree' structure representing the so-called
main variant of the ops type, see my h2hc13 presentation for details) and
since this happens early in the frontend, the const violations will be
reported by the compiler just like as it would otherwise report such source
level problems.
this way one can simply put a do_const attribute on a type, recompile the
tree and see if the compiler ever reports an error to know if the given
constification attempt is viable for the given type or not (and by finding
the 'bad' assignments one can see where to consider rewriting the code
perhaps, we did this a lot in PaX for example to achieve the current level
of attack surface reduction).
cheers,
PaX Team
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.
