** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Importance: High => Undecided
** Changed in: linux (Ubuntu)
Assignee: Manuel Diewald (diewald) => (unassigned)
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
** Description changed:
+ SRU Justification:
+
+ [Impact]
+
+ In the noble backport of 553d5efeb341f ("perf test: Add a signal handler
+ to kill forked child processes") the parent signal handler modifies the
+ automatic test counter after sigsetjmp(). The compiler therefore warns
+ that the counter may be clobbered by siglongjmp(), and perf promotes the
+ warning to an error.
+
+ [Fix]
+
+ Qualify the counter as volatile, as required for automatic variables
+ that may be modified between setjmp and longjmp.
+
+ [Test Plan]
+
+ Build the perf tool:
+
+ $ make -C tools/perf
+
+ [Where problems could occur]
+
+ Problems would be limited to the perf tool, specifically the sub-command
+ perf test.
+
+ [Original report]
+
Our customer reported a building failure against this cycle, it is
related to the stable patches for tools/perf/tests/builtin-test.c:
cd tools/perf; make -j8
ests/builtin-test.c: In function ‘__cmd_test’:
tests/builtin-test.c:419:13: error: variable ‘i’ might be clobbered by
‘longjmp’ or ‘vfork’ [-Werror=clobbered]
- 419 | int i = 0;
- | ^
+ 419 | int i = 0;
+ | ^
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2171033
Title:
noble: generic kernel got a build failure against
tools/perf/tests/builtin-test.c
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171033/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
