linux-kernel - Re: [PATCH] selftests/ftrace: treat module requirement unmet situation as unsupported

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 29 Apr 2020 22:04:38 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Po-Hsu Lin <po-hsu.lin@...onical.com>
Cc:     linux-kselftest@...r.kernel.org, mingo@...hat.com,
        shuah <shuah@...nel.org>, Colin King <colin.king@...onical.com>,
        Masami Hiramatsu <mhiramat@...nel.org>,
        Xiao Yang <yangx.jy@...fujitsu.com>,
        linux-kernel@...r.kernel.org,
        Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: [PATCH] selftests/ftrace: treat module requirement unmet
 situation as unsupported

On Thu, 30 Apr 2020 09:46:36 +0800
Po-Hsu Lin <po-hsu.lin@...onical.com> wrote:

> > I'm fine with these changes if Masami is. But it is Masami's call as his
> > infrastructure is more sensitive to the return calls than mine. I just run
> > the test and see what passes. I don't actually look at the return codes.  
> Another thing to note is that this will also change the "# of
> unresolved" and "# of unsupported" in the summary at the end of the
> test report.

Understood. In my testing, I have all the modules enabled so I don't worry
about it ;-)

-- Steve