linux-kernel - Re: [PATCH 1/5] ftrace: Support full glob matching

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:   Thu, 20 Oct 2016 11:07:52 +0900
From:   Masami Hiramatsu <mhiramat@...nel.org>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     Shuah Khan <shuah@...nel.org>, linux-kernel@...r.kernel.org,
        Ingo Molnar <mingo@...hat.com>,
        Namhyung Kim <namhyung@...nel.org>,
        Tom Zanussi <tom.zanussi@...ux.intel.com>,
        linux-kselftest@...r.kernel.org
Subject: Re: [PATCH 1/5] ftrace: Support full glob matching

On Wed, 19 Oct 2016 09:20:57 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:

> On Wed, 19 Oct 2016 13:53:36 +0900
> Masami Hiramatsu <mhiramat@...nel.org> wrote:
> 
> > Use glob_match() to support flexible glob wildcards (*,?)
> > and character classes ([) for ftrace.
> > Since the full glob matching is slower than the current
> > partial matching routines(*pat, pat*, *pat*), this leaves
> > those routines and just add MATCH_GLOB for complex glob
> > expression.
> > 
> > e.g.
> > ----
> > [root@...alhost tracing]# echo 'sched*group' > set_ftrace_filter
> > [root@...alhost tracing]# cat set_ftrace_filter
> > sched_free_group
> > sched_change_group
> > sched_create_group
> > sched_online_group
> > sched_destroy_group
> > sched_offline_group
> > [root@...alhost tracing]# echo '[Ss]y[Ss]_*' > set_ftrace_filter
> > [root@...alhost tracing]# head set_ftrace_filter
> > sys_arch_prctl
> > sys_rt_sigreturn
> > sys_ioperm
> > SyS_iopl
> > sys_modify_ldt
> > SyS_mmap
> > SyS_set_thread_area
> > SyS_get_thread_area
> > SyS_set_tid_address
> > sys_fork
> > ----
> 
> Hi Masami,
> 
> Is this any different than your last patch, as I already pulled it into
> my queue. I haven't been able to test it much, as I found that 4.9-rc1
> is failing my tests, and I can't add new code to linux-next till 4.9 is
> stable.

This patch is completely same as the last patch. If you already queued it,
please ignore this [1/5].

And OK, what kind of tests are failed on 4.9-rc1? I though a possible
kernel freeze in 4.8 when I ran ftracetest, but it seemed disappeared
in 4.9-rc1.

Thanks,


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