opcode stressor on arm platforms can corrupt progress counter in shared region

Bug #1632989 reported by Colin Ian King
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
stress-ng (Ubuntu)
Fix Released
Medium
Colin Ian King

Bug Description

The opcode stressor generates a random mix of opcodes that can sometimes generate code that trashes the stress-ng shared memory region that contains stress-ng state across processes/threads. This results in weird results in the progress bogo ops/counters being trashed. Fix this by unmapping this region in the opcode stressor child process.

Revision history for this message
Colin Ian King (colin-king) wrote :
Changed in stress-ng (Ubuntu):
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Colin Ian King (colin-king)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package stress-ng - 0.06.17-1ubuntu3

---------------
stress-ng (0.06.17-1ubuntu3) yakkety; urgency=medium

  * Actually include the patches for the following fixes (previous upload didn't
    have them).
  - stress-opcode: unmap the shared region to avoid clobbering it (LP: #1632989)
  - stress-icache: ensure we mprotect on page aligned boundary (LP: #1632991)

 -- Colin King <email address hidden> Thu, 13 Oct 2016 10:13:00 +0100

Changed in stress-ng (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.