From: Catalin Marinas <catalin.marinas@arm.com>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org,
Alexander Potapenko <glider@google.com>, Qian Cai <cai@lca.pw>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
will@kernel.org
Subject: Re: [PATCH] arm64: Move jump_label_init() before parse_early_param()
Date: Thu, 27 Jun 2019 17:25:05 +0100 [thread overview]
Message-ID: <20190627162505.GD9894@arrakis.emea.arm.com> (raw)
In-Reply-To: <201906270856.8CF50064@keescook>
On Thu, Jun 27, 2019 at 08:58:03AM -0700, Kees Cook wrote:
> On Thu, Jun 27, 2019 at 09:02:08AM +0100, Catalin Marinas wrote:
> > On Wed, Jun 26, 2019 at 01:51:15PM -0700, Kees Cook wrote:
> > > This moves arm64 jump_label_init() from smp_prepare_boot_cpu() to
> > > setup_arch(), as done already on x86, in preparation from early param
> > > usage in the init_on_alloc/free() series:
> > > https://lkml.kernel.org/r/1561572949.5154.81.camel@lca.pw
> >
> > This looks fine to me. Is there any other series to be merged soon that
> > depends on this patch (the init_on_alloc/fail one)? If not, I can queue
> > it for 5.3.
>
> Yes, but that series will be in 5.3 also, so there's rush for 5.2. Do
> you want Alexander (via akpm) to include it in his series instead of it going
> through the arm64 tree?
It's pretty late for 5.2, especially since it hasn't had extensive
testing (though I'm fairly sure it won't break). Anyway, it's better if
it goes together with Alexander's series.
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
next prev parent reply other threads:[~2019-06-27 16:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 20:51 [PATCH] arm64: Move jump_label_init() before parse_early_param() Kees Cook
2019-06-27 7:30 ` Ard Biesheuvel
2019-06-27 8:02 ` Catalin Marinas
2019-06-27 15:58 ` Kees Cook
2019-06-27 16:25 ` Catalin Marinas [this message]
2019-06-28 9:26 ` Alexander Potapenko
2019-06-28 14:38 ` 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=20190627162505.GD9894@arrakis.emea.arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=cai@lca.pw \
--cc=glider@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox