linux-kernel - Re: [for-next][PATCH 12/16] kprobes: Initialize kprobes at postcore

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Wed, 3 Jul 2019 10:25:04 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Masami Hiramatsu <mhiramat@...nel.org>
Cc:     Catalin Marinas <catalin.marinas@....com>,
        Mark Rutland <mark.rutland@....com>,
        linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [for-next][PATCH 12/16] kprobes: Initialize kprobes at
 postcore_initcall

On Wed, 3 Jul 2019 10:24:02 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:

> On Wed, 3 Jul 2019 15:08:32 +0100
> Catalin Marinas <catalin.marinas@....com> wrote:
> 
> 
> > > +static int __init run_init_test_probes(void)
> > > +{
> > > +	if (run_kprobe_tests)
> > > +		init_test_probes();    
> > 
> > A return 0 here.  
> 
> Will update (would have triggered a failure on my test suite anyway ;-)
> 
> >   
> > > +}
> > > +module_init(run_init_test_probes);    
> > 
> > This does the trick. I prefer your fix as it leaves the arch code
> > unchanged. In case you need it:
> > 
> > Tested-by: Catalin Marinas <catalin.marinas@....com>
> >   
>

Masami,

If you give me an Acked-by, I'll add it to my tree.

-- Steve