** Description changed:
- In the 2024.06.10 SRU cycle, the ftrace:test.d--event--subsystem-
- enable.tc testcases from ubuntu_kselftests_ftrace are failing:
+ SRU Justification
+
+ [Impact]
+ The ftrace tracing subsystem event test has been failing intermittently in
some
+ instances ever since commit 1a4ea83a6e67 ("selftests/ftrace: Limit length in
+ subsystem-enable tests") was backported to our trees.
+
+ [Fix]
+ Clean cherry-pick of 213879061a9c ("selftests/tracing: Fix false failure of
+ subsystem event test").
+
+ [Test]
+ - Launch an AWS c4.large instance running Noble.
+ - Install the generic 6.8 kernel and boot into it.
+ - Clone the noble:linux tree and cd to it.
+ - Go to tools/testing/selftests/ftrace
+ - Run `sudo ./ftracetest test.d/event/subsystem-enable.tc` a couple of times.
+ The test is expected to fail.
+ - Apply this patch and run `sudo ./ftracetest
test.d/event/subsystem-enable.tc`
+ a couple of times again. The test should now always pass.
+
+ [Where problems could occur]
+ Change is limited to the subsystem event test, no problems should occur in the
+ kernel image or modules.
+
+ [Other info]
+ Jammy was affected but got this fix through upstream stable updates. Questing
+ already has this fix as it landed in v6.17.
+
+
+ --- Original bug report ---
+ In the 2024.06.10 SRU cycle, the ftrace:test.d--event--subsystem-enable.tc
testcases from ubuntu_kselftests_ftrace are failing:
=== Ftrace unit tests ===
[1] event tracing - enable/disable with subsystem level files [FAIL]
[2] (instance) event tracing - enable/disable with subsystem level files
[FAIL]
-
# of passed: 0
# of failed: 2
# of unresolved: 0
# of untested: 0
# of unsupported: 0
# of xfailed: 0
# of undefined(test bug): 0
The relevant part from the verbose output is `fail at least fork, exec
and exit events should be recorded`
This was found on these kernels:
- j:aws-fips version 5.15.0-1065.71+fips1 on the m5a.large instance.
- j:gcp-fips version 5.15.0-1064.72+fips1 on the n2d-standard-2 instance.
** Description changed:
SRU Justification
- [Impact]
+ [Impact]
The ftrace tracing subsystem event test has been failing intermittently in
some
instances ever since commit 1a4ea83a6e67 ("selftests/ftrace: Limit length in
subsystem-enable tests") was backported to our trees.
[Fix]
Clean cherry-pick of 213879061a9c ("selftests/tracing: Fix false failure of
subsystem event test").
[Test]
- Launch an AWS c4.large instance running Noble.
- Install the generic 6.8 kernel and boot into it.
- Clone the noble:linux tree and cd to it.
- Go to tools/testing/selftests/ftrace
- Run `sudo ./ftracetest test.d/event/subsystem-enable.tc` a couple of times.
The test is expected to fail.
- Apply this patch and run `sudo ./ftracetest
test.d/event/subsystem-enable.tc`
a couple of times again. The test should now always pass.
[Where problems could occur]
Change is limited to the subsystem event test, no problems should occur in the
kernel image or modules.
[Other info]
Jammy was affected but got this fix through upstream stable updates. Questing
already has this fix as it landed in v6.17.
-
--- Original bug report ---
In the 2024.06.10 SRU cycle, the ftrace:test.d--event--subsystem-enable.tc
testcases from ubuntu_kselftests_ftrace are failing:
=== Ftrace unit tests ===
[1] event tracing - enable/disable with subsystem level files [FAIL]
[2] (instance) event tracing - enable/disable with subsystem level files
[FAIL]
# of passed: 0
# of failed: 2
# of unresolved: 0
# of untested: 0
# of unsupported: 0
# of xfailed: 0
# of undefined(test bug): 0
The relevant part from the verbose output is `fail at least fork, exec
and exit events should be recorded`
This was found on these kernels:
- j:aws-fips version 5.15.0-1065.71+fips1 on the m5a.large instance.
- j:gcp-fips version 5.15.0-1064.72+fips1 on the n2d-standard-2 instance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071861
Title:
ftrace:test.d--event--subsystem-enable.tc fails on some instances
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2071861/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
