This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1873517
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Tags added: focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1873517
Title:
waitid on riscv64 5.4.0-24-generic is behaving incorrectly
Status in linux package in Ubuntu:
Incomplete
Bug description:
waitid returns 0 PID which is unexpected.
uname -a
Linux ubuntu 5.4.0-24-generic #28-Ubuntu SMP Fri Apr 10 15:33:42 UTC 2020
riscv64 riscv64 riscv64 GNU/Linux
./stress-ng --wait 1
stress-ng: info: [33052] defaulting to a 86400 second (1 day, 0.00 secs) run
per stressor
stress-ng: info: [33052] dispatching hogs: 1 wait
stress-ng: fail: [33053] stress-ng-wait: waitid returned PID 0 but expected
PID 33054
stress-ng: fail: [33053] stress-ng-wait: waitid returned si_signo 0 (signal
0) but expected SIGCHLD
stress-ng: fail: [33053] stress-ng-wait: waitid returned unexpected si_code 0
stress-ng: fail: [33053] stress-ng-wait: waitid returned PID 0 but expected
PID 33054
stress-ng: fail: [33053] stress-ng-wait: waitid returned si_signo 0 (signal
0) but expected SIGCHLD
info: 5 failures reached, aborting stress process
stress-ng: fail: [33053] stress-ng-wait: waitid returned unexpected si_code 0
stress-ng: error: [33052] process 33053 (stress-ng-wait) terminated with an
error, exit status=1 (stress-ng core failure)
stress-ng: info: [33052] unsuccessful run completed in 0.07s
The call in stress-ng is just:
wret = waitid(P_PID, pid_r, &info, options);
..and it checks if the info struct is being populated correctly, which
it appears not to and gets a zero'd info struct.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873517/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
