From: P J P <ppandit@redhat.com>
To: kernel-hardening@lists.openwall.com
Cc: Florian Weimer <fweimer@redhat.com>, P J P <pjp@fedoraproject.org>
Subject: [PATCH 0/1] Zero initialise kernel stack variables
Date: Tue, 27 Feb 2018 16:45:31 +0530 [thread overview]
Message-ID: <20180227111532.1144-1-ppandit@redhat.com> (raw)
From: P J P <pjp@fedoraproject.org>
Hello,
Please see:
-> https://gcc.gnu.org/ml/gcc-patches/2014-06/msg00615.html
This experimental patch by Florian Weimer(CC'd) adds an option
'-finit-local-vars' to gcc(1) compiler. When a program(or kernel)
is built using this option, its automatic(local) variables are
initialised with zero(0). This could significantly reduce the kernel
information leakage issues.
A dnf(8) repository of the latest gcc-7.3.1 package built with the above
patch and kernel-4.15.5 package built using '-finit-local-vars' option
on Fedora-27 is available below
-> https://pjp.fedorapeople.org/init-vars/
This same kernel is running on my F27 test machine as I write this.
There is no slowness or notice-able performance impact as such.
The patch here adds a kbuild menu option to enable/disable '-finit-local-vars'
compiler flag while building the Linux kernel.
I'd appreciate your review and/or inputs to test this option further.
Thank you.
--
Prasad J Pandit / Red Hat Product Security Team (1):
Add an option to build kernel with -finit-local-vars
Makefile | 4 ++++
lib/Kconfig.debug | 8 ++++++++
2 files changed, 12 insertions(+)
--
2.14.3
next reply other threads:[~2018-02-27 11:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 11:15 P J P [this message]
2018-02-27 11:15 ` [PATCH 1/1] Add an option to build kernel with -finit-local-vars P J P
2018-02-27 19:22 ` Laura Abbott
2018-02-27 19:33 ` Kees Cook
2018-02-28 5:49 ` P J P
2018-02-27 19:28 ` [PATCH 0/1] Zero initialise kernel stack variables Kees Cook
2018-02-27 23:26 ` Laura Abbott
2018-02-27 23:38 ` Kees Cook
2018-02-28 6:22 ` P J P
2018-02-28 8:25 ` Florian Weimer
2018-02-28 6:04 ` P J P
2018-03-02 19:52 ` Nick Kralevich
2018-03-02 21:01 ` Casey Schaufler
2018-03-05 20:42 ` 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=20180227111532.1144-1-ppandit@redhat.com \
--to=ppandit@redhat.com \
--cc=fweimer@redhat.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=pjp@fedoraproject.org \
/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.