[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGXu5jJA03Gfgvt05QMoG-pPi7TBaY983HXC1i3DQcOJfx+d_Q@mail.gmail.com>
Date: Wed, 4 Jan 2017 14:30:59 -0800
From: Kees Cook <keescook@...omium.org>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: Julia Lawall <julia.lawall@...6.fr>, devel@...verdev.osuosl.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Bruno Faccini <bruno.faccini@...el.com>,
Oleg Drokin <oleg.drokin@...el.com>,
Vitaly Fertman <vitaly_fertman@...atex.com>,
Joe Perches <joe@...ches.com>,
Andreas Dilger <andreas.dilger@...el.com>,
"John L. Hammond" <john.hammond@...el.com>,
Bruce Korb <bruce.korb@...il.com>,
Emoly Liu <emoly.liu@...el.com>
Subject: Re: Designated initializers, struct randomization and addressing?
On Wed, Jan 4, 2017 at 8:55 AM, Stephen Hemminger
<stephen@...workplumber.org> wrote:
> On Tue, 3 Jan 2017 22:35:26 -0800
> Kees Cook <keescook@...omium.org> wrote:
>
>> For randstruct and constify, the automatic selection is done on
>> structures with only function pointers. (Additional structures can be
>> added via a compiler attribute marking.)
>>
>> See is_pure_ops_struct():
>
> Is there anyway to use this plugin to identify pure_ops structures not already marked as const?
That's what the constify plugin does, yes. Though to deal with cases
where something rarely written to, the
pax_open_kernel/pax_close_kernel annotations are needed, which is why
I don't have a sane port of the constify plugin yet. We need to build
upstream-acceptable infrastructure for the write-rarely case. But, as
Julia replied, yes, there's a huge list. :)
-Kees
--
Kees Cook
Nexus Security
Powered by blists - more mailing lists