All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Laura Abbott <labbott@redhat.com>
Cc: "kernel-hardening@lists.openwall.com" 
	<kernel-hardening@lists.openwall.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Arnd Bergmann <arnd@arndb.de>, Emese Revfy <re.emese@gmail.com>,
	Josh Triplett <josh@joshtriplett.org>,
	PaX Team <pageexec@freemail.hu>,
	Brad Spengler <spender@grsecurity.net>,
	Michal Marek <mmarek@suse.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	minipli@ld-linux.so, Russell King <linux@armlinux.org.uk>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	David Brown <david.brown@linaro.org>,
	"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jeff Layton <jlayton@poochiereds.net>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH v4 0/4] Introduce the initify gcc plugin
Date: Tue, 3 Jan 2017 16:23:57 -0800	[thread overview]
Message-ID: <CAGXu5j+7=h1UB0GGpRg3i1sWdntaDPHMFDZ8rF6hWXriT5J5Eg@mail.gmail.com> (raw)
In-Reply-To: <2b452e83-d74a-8d41-1f00-1764b2c767f1@redhat.com>

On Mon, Dec 19, 2016 at 10:24 AM, Laura Abbott <labbott@redhat.com> wrote:
> I gave this a spin on arm64 and it seems to boot up and run okay
> with just the "select HAVE_GCC_PLUGIN_INITIFY_INIT_EXIT if GCC_PLUGINS"
> added for arm64. The patches could probably use more review but
> I think it would be good to just fold this in for arm64 for ease of
> testing.

Thanks! I've added this to arm64 for a v5 soon.

-Kees

-- 
Kees Cook
Nexus Security

WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: Laura Abbott <labbott@redhat.com>
Cc: "kernel-hardening@lists.openwall.com"
	<kernel-hardening@lists.openwall.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Arnd Bergmann <arnd@arndb.de>, Emese Revfy <re.emese@gmail.com>,
	Josh Triplett <josh@joshtriplett.org>,
	PaX Team <pageexec@freemail.hu>,
	Brad Spengler <spender@grsecurity.net>,
	Michal Marek <mmarek@suse.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	minipli@ld-linux.so, Russell King <linux@armlinux.org.uk>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	David Brown <david.brown@linaro.org>,
	"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jeff Layton <jlayton@poochiereds.net>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: [kernel-hardening] Re: [PATCH v4 0/4] Introduce the initify gcc plugin
Date: Tue, 3 Jan 2017 16:23:57 -0800	[thread overview]
Message-ID: <CAGXu5j+7=h1UB0GGpRg3i1sWdntaDPHMFDZ8rF6hWXriT5J5Eg@mail.gmail.com> (raw)
In-Reply-To: <2b452e83-d74a-8d41-1f00-1764b2c767f1@redhat.com>

On Mon, Dec 19, 2016 at 10:24 AM, Laura Abbott <labbott@redhat.com> wrote:
> I gave this a spin on arm64 and it seems to boot up and run okay
> with just the "select HAVE_GCC_PLUGIN_INITIFY_INIT_EXIT if GCC_PLUGINS"
> added for arm64. The patches could probably use more review but
> I think it would be good to just fold this in for arm64 for ease of
> testing.

Thanks! I've added this to arm64 for a v5 soon.

-Kees

-- 
Kees Cook
Nexus Security

  reply	other threads:[~2017-01-04  0:24 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16 22:06 [PATCH v4 0/4] Introduce the initify gcc plugin Kees Cook
2016-12-16 22:06 ` [kernel-hardening] " Kees Cook
2016-12-16 22:06 ` [PATCH v4 1/4] gcc-plugins: Add " Kees Cook
2016-12-16 22:06   ` [kernel-hardening] " Kees Cook
2016-12-16 22:45   ` PaX Team
2016-12-16 22:45     ` [kernel-hardening] " PaX Team
2016-12-16 22:45     ` PaX Team
2016-12-16 23:02     ` Kees Cook
2016-12-16 23:02       ` [kernel-hardening] " Kees Cook
2016-12-16 23:02       ` Kees Cook
2016-12-16 23:15       ` PaX Team
2016-12-16 23:15         ` [kernel-hardening] " PaX Team
2016-12-16 23:15         ` PaX Team
2016-12-16 22:06 ` [PATCH v4 2/4] util: Move type casts into is_kernel_rodata Kees Cook
2016-12-16 22:06   ` [kernel-hardening] " Kees Cook
2016-12-16 22:06 ` [PATCH v4 3/4] initify: Mark functions with the __nocapture attribute Kees Cook
2016-12-16 22:06   ` [kernel-hardening] " Kees Cook
2016-12-16 22:06 ` [PATCH v4 4/4] initify: Mark functions with the __unverified_nocapture attribute Kees Cook
2016-12-16 22:06   ` [kernel-hardening] " Kees Cook
2016-12-16 22:19 ` [PATCH v4 0/4] Introduce the initify gcc plugin Kees Cook
2016-12-16 22:19   ` [kernel-hardening] " Kees Cook
2016-12-16 22:19   ` Kees Cook
2016-12-19 11:10   ` Emese Revfy
2016-12-19 11:10     ` [kernel-hardening] " Emese Revfy
2016-12-19 11:10     ` Emese Revfy
2017-01-04  0:23     ` Kees Cook
2017-01-04  0:23       ` [kernel-hardening] " Kees Cook
2017-01-04  0:23       ` Kees Cook
2017-01-11  0:24       ` Emese Revfy
2017-01-11  0:24         ` [kernel-hardening] " Emese Revfy
2017-01-11  0:24         ` Emese Revfy
2017-01-11  1:09         ` Kees Cook
2017-01-11  1:09           ` [kernel-hardening] " Kees Cook
2017-01-11  1:09           ` Kees Cook
2017-01-12 21:41           ` Emese Revfy
2017-01-12 21:41             ` [kernel-hardening] " Emese Revfy
2017-01-12 21:41             ` Emese Revfy
2017-01-12 23:27             ` Kees Cook
2017-01-12 23:27               ` [kernel-hardening] " Kees Cook
2017-01-12 23:27               ` Kees Cook
2017-01-12 23:40               ` Kees Cook
2017-01-12 23:40                 ` [kernel-hardening] " Kees Cook
2017-01-12 23:40                 ` Kees Cook
2017-01-17 20:31                 ` Emese Revfy
2017-01-17 20:31                   ` [kernel-hardening] " Emese Revfy
2017-01-17 20:31                   ` Emese Revfy
2017-01-19  1:22                   ` Kees Cook
2017-01-19  1:22                     ` [kernel-hardening] " Kees Cook
2017-01-19  1:22                     ` Kees Cook
2017-02-15  0:23                 ` Emese Revfy
2017-02-15  0:23                   ` [kernel-hardening] " Emese Revfy
2017-02-15  0:23                   ` Emese Revfy
2017-02-15 19:27                   ` Kees Cook
2017-02-15 19:27                     ` [kernel-hardening] " Kees Cook
2017-02-15 19:27                     ` Kees Cook
2017-02-20 21:42                     ` Emese Revfy
2017-02-20 21:42                       ` [kernel-hardening] " Emese Revfy
2017-02-20 21:42                       ` Emese Revfy
2016-12-19 18:24 ` Laura Abbott
2016-12-19 18:24   ` [kernel-hardening] " Laura Abbott
2017-01-04  0:23   ` Kees Cook [this message]
2017-01-04  0:23     ` Kees Cook
2017-01-04  0:23     ` 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='CAGXu5j+7=h1UB0GGpRg3i1sWdntaDPHMFDZ8rF6hWXriT5J5Eg@mail.gmail.com' \
    --to=keescook@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --cc=catalin.marinas@arm.com \
    --cc=david.brown@linaro.org \
    --cc=jlayton@poochiereds.net \
    --cc=josh@joshtriplett.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=labbott@redhat.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linux@rasmusvillemoes.dk \
    --cc=minipli@ld-linux.so \
    --cc=mmarek@suse.com \
    --cc=pageexec@freemail.hu \
    --cc=re.emese@gmail.com \
    --cc=sam@ravnborg.org \
    --cc=spender@grsecurity.net \
    --cc=tglx@linutronix.de \
    --cc=yamada.masahiro@socionext.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.