stress-ng opcode test should run with call capabilities disabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
stress-ng (Ubuntu) |
Fix Released
|
Medium
|
Colin Ian King |
Bug Description
I use stress-ng to stress CPU(Xeon E3, CentOS7). During the test, I found that system clock has been modified to 1970 or 1969 strangely, but this modification has no effect to rtc. For a tough debug, found stress-opcode cause this modification, below is the code
((void (*)(void)
And I limit test to opcode only, like this :
./stress-ng --opcode 0 --timeout 3m --log-file log/opcode.log
The test also cause different results, like user logout, gibberish output and so on. Can anyone explain this test, I have read some short description about opcode in cpu.job, but still question how the test code work. For the system time is changed, but the test past, how can I how if the system work correctly or not?
Fix committed: 740b5b85c6ab102 53765f02c7adc25 6c5fc18dc2 ("stress-opcode: drop all capabilities so we can't do much damage")