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, 3 Jul 2017 11:59:06 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Masami Hiramatsu <mhiramat@...nel.org>
Cc:     linux-kselftest@...r.kernel.org, shuah@...nel.org,
        Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
        naresh.kamboju@...aro.org
Subject: Re: [PATCH 1/2] selftests: ftrace: Do not failure if there is
 unsupported tests

On Tue, 4 Jul 2017 00:52:32 +0900
Masami Hiramatsu <mhiramat@...nel.org> wrote:
> 
> > 
> > Can we add an option in kselftest, or to ftracetest that decides if
> > unsupported is a failure or not? Otherwise I can not ack this patch.  
> 
> I would rather like to add an option to ftracetest instead of
> kselftest, because whether the tested feature should be supported
> or not is hard to decide from testing framework. It should be
> checked by manual.

Can we do both? That is, add an option to have ftracetest not fail on
"unsupported" but have it fail by default. We can have kselftest just
pass in a parameter to ftracetest that has unsupported not fail?

But if that is too difficult, then I can live with modifying my test
case to add the option.

-- Steve

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ