All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
	devel@driverdev.osuosl.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Bruno Faccini <bruno.faccini@intel.com>,
	Oleg Drokin <oleg.drokin@intel.com>,
	Vitaly Fertman <vitaly_fertman@xyratex.com>,
	Joe Perches <joe@perches.com>,
	Andreas Dilger <andreas.dilger@intel.com>,
	"John L. Hammond" <john.hammond@intel.com>,
	Bruce Korb <bruce.korb@gmail.com>,
	Emoly Liu <emoly.liu@intel.com>
Subject: Re: Designated initializers, struct randomization and addressing?
Date: Wed, 4 Jan 2017 14:30:59 -0800	[thread overview]
Message-ID: <CAGXu5jJA03Gfgvt05QMoG-pPi7TBaY983HXC1i3DQcOJfx+d_Q@mail.gmail.com> (raw)
In-Reply-To: <20170104085534.7c4d2b07@xeon-e3>

On Wed, Jan 4, 2017 at 8:55 AM, Stephen Hemminger
<stephen@networkplumber.org> wrote:
> On Tue, 3 Jan 2017 22:35:26 -0800
> Kees Cook <keescook@chromium.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

      parent reply	other threads:[~2017-01-04 22:31 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-17  1:00 [PATCH] staging: lustre: ldlm: use designated initializers Kees Cook
2016-12-17  1:00 ` [lustre-devel] " Kees Cook
2016-12-19 16:22 ` James Simmons
2016-12-19 16:22   ` [lustre-devel] " James Simmons
2016-12-19 16:47   ` Bruce Korb
2016-12-19 16:48     ` [lustre-devel] " Bruce Korb
2016-12-19 17:12     ` James Simmons
2016-12-19 17:12       ` [lustre-devel] " James Simmons
2016-12-20  7:10     ` Dan Carpenter
2016-12-20  7:10       ` [lustre-devel] " Dan Carpenter
2016-12-20 14:57       ` Hammond, John
2016-12-20 14:57         ` [lustre-devel] " Hammond, John
2016-12-20 16:47         ` Bruce Korb
2016-12-20 16:48           ` [lustre-devel] " Bruce Korb
2016-12-20 18:52           ` Dan Carpenter
2016-12-20 18:52             ` [lustre-devel] " Dan Carpenter
2016-12-20 19:07         ` Dan Carpenter
2016-12-20 19:07           ` [lustre-devel] " Dan Carpenter
2016-12-20 19:46           ` Kees Cook
2016-12-20 19:46             ` [lustre-devel] " Kees Cook
2016-12-19 16:50   ` Patrick Farrell
2016-12-19 17:11     ` James Simmons
2016-12-19 17:11       ` James Simmons
2016-12-20 10:40   ` Dan Carpenter
2016-12-20 10:40     ` [lustre-devel] " Dan Carpenter
2016-12-20 17:29 ` Designated initializers, struct randomization and addressing? Joe Perches
2016-12-20 17:29   ` [lustre-devel] " Joe Perches
2017-01-03 23:47   ` Kees Cook
2017-01-03 23:55     ` Bruce Korb
2017-01-04  0:13       ` Kees Cook
2017-01-04  6:27     ` Julia Lawall
2017-01-04  6:35       ` Kees Cook
2017-01-04 16:55         ` Stephen Hemminger
2017-01-04 17:37           ` Julia Lawall
2017-01-04 22:30           ` Kees Cook [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGXu5jJA03Gfgvt05QMoG-pPi7TBaY983HXC1i3DQcOJfx+d_Q@mail.gmail.com \
    --to=keescook@chromium.org \
    --cc=andreas.dilger@intel.com \
    --cc=bruce.korb@gmail.com \
    --cc=bruno.faccini@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=emoly.liu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=john.hammond@intel.com \
    --cc=julia.lawall@lip6.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg.drokin@intel.com \
    --cc=stephen@networkplumber.org \
    --cc=vitaly_fertman@xyratex.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.