linux-kernel - Re: [PATCH] arm64: Move jump_label_init() before parse_early

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <201906270856.8CF50064@keescook>
Date:   Thu, 27 Jun 2019 08:58:03 -0700
From:   Kees Cook <keescook@...omium.org>
To:     Catalin Marinas <catalin.marinas@....com>
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>
Subject: Re: [PATCH] arm64: Move jump_label_init() before parse_early_param()

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?

-- 
Kees Cook