[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190627162505.GD9894@arrakis.emea.arm.com>
Date: Thu, 27 Jun 2019 17:25:05 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: Kees Cook <keescook@...omium.org>
Cc: linux-kernel@...r.kernel.org,
Alexander Potapenko <glider@...gle.com>, Qian Cai <cai@....pw>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Andrew Morton <akpm@...ux-foundation.org>, will@...nel.org
Subject: Re: [PATCH] arm64: Move jump_label_init() before parse_early_param()
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@....com>
Powered by blists - more mailing lists