From: Alexander Potapenko <glider@google.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Kees Cook <keescook@chromium.org>,
LKML <linux-kernel@vger.kernel.org>, 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: Fri, 28 Jun 2019 11:26:34 +0200 [thread overview]
Message-ID: <CAG_fn=UhdoyWjFPxdFOJ7XFRHb62RErxFjOKnFeHtMJWTib7pg@mail.gmail.com> (raw)
In-Reply-To: <20190627162505.GD9894@arrakis.emea.arm.com>
On Thu, Jun 27, 2019 at 6:25 PM Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> 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.
Am I understanding right this is already covered by Kees having sent
his patch to -mm tree and I don't need to explicitly include it into
my series?
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
--
Alexander Potapenko
Software Engineer
Google Germany GmbH
Erika-Mann-Straße, 33
80636 München
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
next prev parent reply other threads:[~2019-06-28 9:26 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
2019-06-28 9:26 ` Alexander Potapenko [this message]
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='CAG_fn=UhdoyWjFPxdFOJ7XFRHb62RErxFjOKnFeHtMJWTib7pg@mail.gmail.com' \
--to=glider@google.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=cai@lca.pw \
--cc=catalin.marinas@arm.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;
as well as URLs for NNTP newsgroup(s).