[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170104085534.7c4d2b07@xeon-e3>
Date: Wed, 4 Jan 2017 08:55:34 -0800
From: Stephen Hemminger <stephen@...workplumber.org>
To: Kees Cook <keescook@...omium.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 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?
Powered by blists - more mailing lists