All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Micay <danielmicay@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: Christoph Lameter <cl@linux.com>,
	Kees Cook <keescook@chromium.org>,
	kernel-hardening@lists.openwall.com
Subject: [kernel-hardening] Re: [PATCH] mark most percpu globals as __ro_after_init
Date: Wed, 10 May 2017 14:31:31 -0400	[thread overview]
Message-ID: <1494441091.4602.1.camel@gmail.com> (raw)
In-Reply-To: <1494439172.1255.1.camel@gmail.com>

> Booted / did some stuff on x86 (it's running right now), and currently
> building it for a 3.18 arm64 kernel to test there.

Yeah, confirmed to work on an Android 3.18 arm64 kernel (Pixel phone)
too in addition to 4.11 and master for x86_64.

  reply	other threads:[~2017-05-10 18:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 17:36 [kernel-hardening] [PATCH] mark most percpu globals as __ro_after_init Daniel Micay
2017-05-10 17:52 ` [kernel-hardening] " Tejun Heo
2017-05-10 17:59   ` Daniel Micay
2017-05-10 18:31     ` Daniel Micay [this message]
2017-05-10 19:20     ` Tejun Heo
2017-05-10 18:16 ` Kees Cook
2017-05-10 18:16   ` 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=1494441091.4602.1.camel@gmail.com \
    --to=danielmicay@gmail.com \
    --cc=cl@linux.com \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=tj@kernel.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.