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]
Date:	Sun, 05 Oct 2014 11:08:04 +0900
From:	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Shuah Khan <shuah.kh@...sung.com>,
	Tom Zanussi <tom.zanussi@...ux.intel.com>,
	Oleg Nesterov <oleg@...hat.com>,
	Namhyung Kim <namhyung@...nel.org>,
	Fengguang Wu <fengguang.wu@...el.com>,
	Ingo Molnar <mingo@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Re: (ltc-kernel 10162) Re: [PATCH ftrace/for-next v6] ftracetest:
 Add POSIX.3 standard and XFAIL result codes

(2014/10/04 5:53), Steven Rostedt wrote:
> On Fri, 03 Oct 2014 20:29:12 +0900
> Masami Hiramatsu <masami.hiramatsu.pt@...achi.com> wrote:
> 
>> Ping? :)
> 
> Just to make sure. This is just the one patch that I missed before,
> right?

Yes, this one is the last patch in previous series.

> 
> I pulled it and now testing it (running the tests). I'll push it to my
> linux-next branch sometime later today. You'll probably see it as you
> wake up ;-)

Thanks!!

> 
> -- Steve
> 
>>
>> (2014/09/29 21:11), Masami Hiramatsu wrote:
>>> Steven, could you pick this instead of old v5 patch?
>>>
>>> As you pointed, this version shows the log of "unsuppoted" test result.
>>>
>>> Thank you,
>>>
>>> (2014/09/29 21:02), Masami Hiramatsu wrote:
>>>> Add XFAIL and POSIX 1003.3 standard codes (UNRESOLVED/
>>>> UNTESTED/UNSUPPORTED) as result codes. These are used for the
>>>> results that test case is expected to fail or unsupported
>>>> feature (by config).
>>>>
>>>> To return these result code, this introduces exit_unresolved,
>>>> exit_untested, exit_unsupported and exit_xfail functions,
>>>> which use real-time signals to notify the result code to
>>>> ftracetest.
>>>>
>>>> This also set "errexit" option for the testcases, so that
>>>> the tests don't need to exit explicitly.
>>>>
>>>> Note that if the test returns UNRESOLVED/UNSUPPORTED/FAIL,
>>>> its test log including executed commands is shown on console
>>>> and main logfile as below.
> --
> 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/
> 


-- 
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@...achi.com


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ