Comment 0 for bug 1929527

Revision history for this message
Po-Hsu Lin (cypressyew) wrote : Skip unsupported kprobe-direct.tc and kprobe_args_user.tc in kselftest/ftrace

[Impact]
These two tests will be marked as "unresolved" and once causing failures in our ubuntu_kernel_selftests (lp:1869227)

Our workaround is to blacklist this test in autotest-client-tests [1]

With patch b730d668138cb3 ("ftrace/selftest: make unresolved cases cause failure if --fail-unresolved set") available, an unresolved case will not be treated as a failure unless we requested so.

[1] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py?id=a381d47a9004388730e825cd20566ef102a29399

[Fix]
* 1e11b7dbef17bb selftests/ftrace: Return unsupported for the unconfigured features

[Test]
Tested on s390x / PowerPC, this will be marked as unsupported:
$ sudo ./ftracetest test.d/kprobe/kprobe_args_user.tc
=== Ftrace unit tests ===
[1] Kprobe event user-memory access [UNSUPPORTED]

# of passed: 0
# of failed: 0
# of unresolved: 0
# of untested: 0
# of unsupported: 1
# of xfailed: 0
# of undefined(test bug): 0
$ echo $?
0

[Where problems could occur]
Changes limited to testing tool, should not impact real kernel functionality. After this patch has landed in our kernel we can remove the local workaround in autotest-client-tests. We might see failures in s390x / PowerPC in the future.