Public bug reported:
Commits below added re-do loops that can get stuck forever
6f87db7031632554 stress-sysfs: add some illegal read calls to see if we can
break sysfs
f4af122d7d081795 stress-procfs: add some illegal read calls to see if we can
break procfs
This can be triggered if we are running multiple procfs or sysfs
stressors as root and we hit a SIGALRM from the -t option and we are in
the new extra stress read call code paths that were added by the above
commits.
Fix committed: 35e6642a6f72fa8a2dd650b8ce89074ee8a91500 ("stress-
procfs/sysfs: abort rather than re-doing reads on read errors")
** Affects: stress-ng (Ubuntu)
Importance: High
Assignee: Colin Ian King (colin-king)
Status: Fix Committed
** Changed in: stress-ng (Ubuntu)
Status: New => Fix Committed
** Changed in: stress-ng (Ubuntu)
Importance: Undecided => High
** Changed in: stress-ng (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Summary changed:
- procfs and sysfs stressors can get caught in an infitinite loop on EINTR or
EAGAIN read errors
+ procfs and sysfs stressors can get caught in an infinite loop on EINTR or
EAGAIN read errors
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629843
Title:
procfs and sysfs stressors can get caught in an infinite loop on EINTR
or EAGAIN read errors
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1629843/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
