linux-kernel - Re: [PATCH] kprobes: Fix to init kprobes in subsys

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: <20190613160857.9db38d1cb32996b8c4e0ddc3@kernel.org>
Date:   Thu, 13 Jun 2019 16:08:57 +0900
From:   Masami Hiramatsu <mhiramat@...nel.org>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     Anders Roxell <anders.roxell@...aro.org>,
        Ingo Molnar <mingo@...nel.org>,
        "Naveen N . Rao" <naveen.n.rao@...ux.ibm.com>,
        Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>,
        "David S . Miller" <davem@...emloft.net>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kprobes: Fix to init kprobes in subsys_initcall

On Wed, 12 Jun 2019 09:47:29 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:

> On Wed, 12 Jun 2019 16:59:47 +0900
> Masami Hiramatsu <mhiramat@...nel.org> wrote:
> 
> > Hi Steve,
> > 
> > Could you pick this to your ftrace/core branch?
> 
> "core" or should this go to "urgent"? The difference is that core is
> scheduled for the next merge window, and urgent is for the rc releases
> (ie. bug fixes).

If the previous one (b5f8b32c93b2) has already gone to rc, yes
this should be in urgent, since this always crashes arm64 kernel
if we enables CONFIG_KPROBES_SANITY_TEST.

Thank you,


-- 
Masami Hiramatsu <mhiramat@...nel.org>