linux-kernel - Re: [PATCH 2/2 v3] ftracetest: Add a couple of ftrace test cases

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, 5 Nov 2014 17:53:50 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc:	Namhyung Kim <namhyung@...nel.org>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 2/2 v3] ftracetest: Add a couple of ftrace test cases

On Wed, 05 Nov 2014 17:41:15 +0900
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com> wrote:

> (2014/11/05 16:52), Namhyung Kim wrote:
> > Hi Steve,
> > 
> > On Tue, 04 Nov 2014 10:28:47 -0500, Steven Rostedt wrote:
> >> +count=`cat trace | grep '()' | grep -v schedule | wc -l`
> >> +
> >> +if [ $count -ne 0 ]; then
> >> +    echo "Graph filtering not working after stack tracer disabled?"
> >> +    exit -1
> >> +fi
> >> +
> >> +count=`cat trace | grep 'schedule()' | wc -l` 
> >> +if [ $count -eq 0 ]; then
> >> +    echo "No schedule traces found?"
> >> +    exit -1
> > 
> > Hmm.. in this case don't we need to call do_reset especially for the
> > last testcase?  Maybe we could define a simple function like:
> > 
> > fail() { # msg
> > 	do_reset
> > 	echo $1
> > 	exit -1
> > }
> 
> If you want to call do_reset always on exit, you can also use "trap do_reset 0" too.

Cool, I didn't know that. But I like the "fail" command, as it is a bit
more verbose.

I'll update.

Thanks,

-- 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/