linux-kernel - Re: [RFC PATCH 0/4 v2] ftracetests: Add ftrace tests to ftracetests

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] [day] [month] [year] [list]

Message-ID: <20141104090357.37531ed3@gandalf.local.home>
Date:	Tue, 4 Nov 2014 09:03:57 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [RFC PATCH 0/4 v2] ftracetests: Add ftrace tests to ftracetests

On Tue, 04 Nov 2014 18:30:37 +0900
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com> wrote:

> (2014/11/04 6:27), Steven Rostedt wrote:
> > Second attempt. I took the advice from Masami Hiramatsu and modified
> > my tests. I also added some helper functions to ftracetests as well.
> > 
> > I split the one function graph test into two. One to just test the
> > filtering of the function graph and another to test with stack tracer.
> > 
> > Steven Rostedt (Red Hat) (4):
> >       ftracetest: Add clear_trace() helper to reset the trace file
> >       ftracetest: Add disable/enable_tracing() helper calls
> >       ftracetest: Add helper reset_tracer() function
> 
> BTW, I think you can fold these patches into one. No need to separate
> for each helper functions.

Yeah, I probably should. I did those each at different times, and just
put them in separately.

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/