linux-kernel - Re: [PATCH 2/4] ftrace/instances: Clear function triggers when removing instances

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:   Mon, 15 May 2017 12:11:03 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     "Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com>
Cc:     Shuah Khan <shuah@...nel.org>,
        Michael Ellerman <mpe@...erman.id.au>,
        linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
        Masami Hiramatsu <mhiramat@...nel.org>
Subject: Re: [PATCH 2/4] ftrace/instances: Clear function triggers when
 removing instances

On Mon, 15 May 2017 11:21:15 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:

> On Sun, 14 May 2017 01:01:02 +0530
> "Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com> wrote:
> 
> > If instance directories are deleted while there are registered function
> > triggers:
> > 
> >   # cd /sys/kernel/debug/tracing/instances
> >   # mkdir test
> >   # echo "schedule:enable_event:sched:sched_switch" > test/set_ftrace_filter
> >   # rmdir test
> >   Unable to handle kernel paging request for data at address 0x00000008
> >   Unable to handle kernel paging request for data at address 0x00000008
> >   Faulting instruction address: 0xc0000000021edde8
> >   Oops: Kernel access of bad area, sig: 11 [#1]
> >   SMP NR_CPUS=2048
> >   NUMA
> >   pSeries  
> 
> Looks like this patch needs to be marked for stable, and go in right
> away. I may also do the same for the ftracetest bashism patch with
> Masami's approval. I may also slip in the ftracetest for the bug that
> this patch fixes.

As this patch fixes a bug that was introduced with the 4.12 merge
window. Thus, it's not stable worthy (stable isn't affected). Although,
I'll wait on Masami to see if that should go to stable.

-- Steve