From: Joe Perches <joe@perches.com>
To: Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org, Julia Lawall <julia.lawall@lip6.fr>,
Dan Carpenter <error27@gmail.com>
Cc: Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
James Simmons <jsimmons@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"John L. Hammond" <john.hammond@intel.com>,
Emoly Liu <emoly.liu@intel.com>,
Vitaly Fertman <vitaly_fertman@xyratex.com>,
Bruno Faccini <bruno.faccini@intel.com>,
Bruce Korb <bruce.korb@gmail.com>,
lustre-devel@lists.lustre.org, devel@driverdev.osuosl.org
Subject: Designated initializers, struct randomization and addressing?
Date: Tue, 20 Dec 2016 09:29:55 -0800 [thread overview]
Message-ID: <1482254995.1984.20.camel@perches.com> (raw)
In-Reply-To: <20161217010045.GA140343@beast>
On Fri, 2016-12-16 at 17:00 -0800, Kees Cook wrote:
> Prepare to mark sensitive kernel structures for randomization by making
sure they're using designated initializers.
About the designated initializer patches,
which by themselves are fine of course,
and the fundamental randomization plugin,
c guarantees that struct member ordering
is as specified.
how is the code to be verified so that
any use of things like offsetof and any
address/indexing is not impacted?
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org, Julia Lawall <julia.lawall@lip6.fr>,
Dan Carpenter <error27@gmail.com>
Cc: Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
James Simmons <jsimmons@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"John L. Hammond" <john.hammond@intel.com>,
Emoly Liu <emoly.liu@intel.com>,
Vitaly Fertman <vitaly_fertman@xyratex.com>,
Bruno Faccini <bruno.faccini@intel.com>,
Bruce Korb <bruce.korb@gmail.com>,
lustre-devel@lists.lustre.org, devel@driverdev.osuosl.org
Subject: [lustre-devel] Designated initializers, struct randomization and addressing?
Date: Tue, 20 Dec 2016 09:29:55 -0800 [thread overview]
Message-ID: <1482254995.1984.20.camel@perches.com> (raw)
In-Reply-To: <20161217010045.GA140343@beast>
On Fri, 2016-12-16 at 17:00 -0800, Kees Cook wrote:
> Prepare to mark sensitive kernel structures for randomization by making
sure they're using designated initializers.
About the designated initializer patches,
which by themselves are fine of course,
and the fundamental randomization plugin,
c guarantees that struct member ordering
is as specified.
how is the code to be verified so that
any use of things like offsetof and any
address/indexing is not impacted?
next prev parent reply other threads:[~2016-12-20 17:30 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 ` Joe Perches [this message]
2016-12-20 17:29 ` [lustre-devel] Designated initializers, struct randomization and addressing? 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
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=1482254995.1984.20.camel@perches.com \
--to=joe@perches.com \
--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=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.hammond@intel.com \
--cc=jsimmons@infradead.org \
--cc=julia.lawall@lip6.fr \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@intel.com \
--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.