| 2021-05-25 08:34:27 |
Po-Hsu Lin |
bug |
|
|
added bug |
| 2021-05-25 08:42:00 |
Po-Hsu Lin |
summary |
Skip unsupported kprobe-direct.tc and kprobe_args_user.tc in kselftest/ftrace |
Skip unsupported kprobe_args_user.tc in kselftest/ftrace |
|
| 2021-05-25 08:50:33 |
Po-Hsu Lin |
description |
[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. |
[Impact]
This kprobe_args_user.tc test will be marked as "unresolved" and once causing failures in ftrace of our ubuntu_kernel_selftests (lp:1869227)
Our workaround is to blacklist this test in autotest-client-tests [1]
Note that 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
With this patch it will be marked as unsupported, easier to understand than unresolved.
This patch needs to be backported on Focal.
[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. |
|
| 2021-05-25 09:01:15 |
Po-Hsu Lin |
description |
[Impact]
This kprobe_args_user.tc test will be marked as "unresolved" and once causing failures in ftrace of our ubuntu_kernel_selftests (lp:1869227)
Our workaround is to blacklist this test in autotest-client-tests [1]
Note that 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
With this patch it will be marked as unsupported, easier to understand than unresolved.
This patch needs to be backported on Focal.
[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. |
[Impact]
This kprobe_args_user.tc test will be marked as "unresolved" and once causing failures in ftrace of our ubuntu_kernel_selftests (lp:1869227)
Our workaround is to blacklist this test in autotest-client-tests [1]
Note that 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
With this patch it will be marked as unsupported, easier to understand than unresolved.
This patch needs to be backported on Focal.
[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. With local workaround in autotest-client-tests removed we might see failures in s390x / PowerPC in the future. |
|
| 2021-05-25 09:01:26 |
Po-Hsu Lin |
description |
[Impact]
This kprobe_args_user.tc test will be marked as "unresolved" and once causing failures in ftrace of our ubuntu_kernel_selftests (lp:1869227)
Our workaround is to blacklist this test in autotest-client-tests [1]
Note that 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
With this patch it will be marked as unsupported, easier to understand than unresolved.
This patch needs to be backported on Focal.
[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. With local workaround in autotest-client-tests removed we might see failures in s390x / PowerPC in the future. |
[Impact]
This kprobe_args_user.tc test will be marked as "unresolved" and once causing failures in ftrace of our ubuntu_kernel_selftests (lp:1869227)
Our workaround is to blacklist this test in autotest-client-tests [1]
Note that 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
With this patch it will be marked as unsupported, easier to understand than unresolved.
This patch needs to be backported on Focal.
[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. With this patch and local workaround in autotest-client-tests removed we might see failures in s390x / PowerPC in the future. |
|
| 2021-05-25 09:16:21 |
Po-Hsu Lin |
description |
[Impact]
This kprobe_args_user.tc test will be marked as "unresolved" and once causing failures in ftrace of our ubuntu_kernel_selftests (lp:1869227)
Our workaround is to blacklist this test in autotest-client-tests [1]
Note that 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
With this patch it will be marked as unsupported, easier to understand than unresolved.
This patch needs to be backported on Focal.
[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. With this patch and local workaround in autotest-client-tests removed we might see failures in s390x / PowerPC in the future. |
[Impact]
This kprobe_args_user.tc test will be marked as "unresolved" and once causing failures in ftrace of our ubuntu_kernel_selftests (lp:1869227)
Our workaround is to blacklist this test in autotest-client-tests [1]
Note that 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
With this patch it will be marked as unsupported, easier to understand than unresolved.
This patch can be found in Groovy and newer releases, and this test does not exist in Bionic and older releases.
[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. With this patch and local workaround in autotest-client-tests removed we might see failures in s390x / PowerPC in the future. |
|
| 2021-05-25 09:29:17 |
Po-Hsu Lin |
summary |
Skip unsupported kprobe_args_user.tc in kselftest/ftrace |
Mark kprobe_args_user.tc in kselftest/ftrace as unsupported |
|
| 2021-05-25 09:43:49 |
Po-Hsu Lin |
bug task added |
|
linux (Ubuntu) |
|
| 2021-05-25 09:44:25 |
Po-Hsu Lin |
nominated for series |
|
Ubuntu Focal |
|
| 2021-05-25 09:44:25 |
Po-Hsu Lin |
bug task added |
|
linux (Ubuntu Focal) |
|
| 2021-05-25 09:44:45 |
Po-Hsu Lin |
bug task added |
|
linux-oem-5.6 (Ubuntu) |
|
| 2021-05-25 09:44:56 |
Po-Hsu Lin |
linux-oem-5.6 (Ubuntu): status |
New |
Invalid |
|
| 2021-05-25 09:45:00 |
Po-Hsu Lin |
linux (Ubuntu): status |
New |
Fix Released |
|
| 2021-05-25 09:45:04 |
Po-Hsu Lin |
linux (Ubuntu Focal): status |
New |
In Progress |
|
| 2021-05-25 09:45:07 |
Po-Hsu Lin |
linux-oem-5.6 (Ubuntu Focal): status |
New |
In Progress |
|
| 2021-05-25 09:45:09 |
Po-Hsu Lin |
ubuntu-kernel-tests: status |
New |
In Progress |
|
| 2021-05-25 09:45:14 |
Po-Hsu Lin |
linux (Ubuntu Focal): assignee |
|
Po-Hsu Lin (cypressyew) |
|
| 2021-05-25 09:45:16 |
Po-Hsu Lin |
ubuntu-kernel-tests: assignee |
|
Po-Hsu Lin (cypressyew) |
|
| 2021-05-25 09:45:21 |
Po-Hsu Lin |
linux-oem-5.6 (Ubuntu Focal): assignee |
|
Po-Hsu Lin (cypressyew) |
|
| 2021-05-26 13:09:50 |
Kleber Sacilotto de Souza |
linux (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2021-06-03 03:30:32 |
Ubuntu Kernel Bot |
tags |
|
verification-needed-focal |
|
| 2021-06-07 10:22:26 |
Po-Hsu Lin |
tags |
verification-needed-focal |
verification-done-focal |
|
| 2021-06-07 10:22:37 |
Po-Hsu Lin |
tags |
verification-done-focal |
5.4 focal ubuntu-kernel-selftests verification-done-focal |
|
| 2021-06-22 16:05:32 |
Launchpad Janitor |
linux (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2021-06-22 16:05:32 |
Launchpad Janitor |
cve linked |
|
2020-24586 |
|
| 2021-06-22 16:05:32 |
Launchpad Janitor |
cve linked |
|
2020-24587 |
|
| 2021-06-22 16:05:32 |
Launchpad Janitor |
cve linked |
|
2020-24588 |
|
| 2021-06-22 16:05:32 |
Launchpad Janitor |
cve linked |
|
2020-26139 |
|
| 2021-06-22 16:05:32 |
Launchpad Janitor |
cve linked |
|
2020-26141 |
|
| 2021-06-22 16:05:32 |
Launchpad Janitor |
cve linked |
|
2020-26145 |
|
| 2021-06-22 16:05:32 |
Launchpad Janitor |
cve linked |
|
2020-26147 |
|
| 2021-06-22 16:05:32 |
Launchpad Janitor |
cve linked |
|
2021-33200 |
|
| 2021-11-22 07:59:07 |
Po-Hsu Lin |
linux-oem-5.6 (Ubuntu Focal): status |
In Progress |
Won't Fix |
|
| 2021-11-22 07:59:17 |
Po-Hsu Lin |
ubuntu-kernel-tests: status |
In Progress |
Fix Released |
|
