This bug was fixed in the package stress-ng - 0.08.13-1
---------------
stress-ng (0.08.13-1) unstable; urgency=medium
* stress-rdrand: use 32 bit rdrand for i386
* stress_drop_capabilities: voidify name to avoid warning
* Enable 64 bit large file system support by default
* debian/rules: Add hardening=+all
* manual: fix several spelling mistakes
* stress-cpu: fix spelling mistake "assigment" -> "assignment"
* stress-ng: fix spelling mistake "afer" -> "after"
* stress-opcode: drop all capabilties so we can't do much
damage (LP: #1714044)
* helper: add stress_drop_capabilities to drop all capabilities
* stress-socket-diag: use new HAVE_SOCK_DIAG_H build time check flag
* Add sock_diag.h auto configure build time checking
* Add sockdiag stressor
* stress-fcntl: fix build failure on SLES11 SP4 (LP: #1709905)
* stress-cyclic: fix build warning on systems w/o atomic ops
* stress-softlockup: fix build warning on systems w/o atomic ops
-- Colin King <[email protected]> Wed, 30 Aug 2017 22:06:11
+0100
** Changed in: stress-ng (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714044
Title:
stress-ng opcode test should run with call capabilities disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1714044/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
