opcode stressor on arm platforms can corrupt progress counter in shared region
Bug #1632989 reported by
Colin Ian King
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.
To post a comment you must log in.
Fix committed, commit: http:// kernel. ubuntu. com/git/ cking/stress- ng.git/ commit/ ?id=a61afb428ab 1dde9f80ba9775c c6a779709dd499