Return code reports success when malloc test fails
Bug #1544575 reported by
Rod Smith
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Stress-ng |
Fix Released
|
High
|
Colin Ian King |
Bug Description
I ran stress-ng 0.05.12 on a 32-bit computer and got the following output:
rodsmith@
stress-ng: info: [5500] dispatching hogs: 2 malloc
*** Error in `stress-ng': free(): invalid next size (fast): 0x07af3fe8 ***
stress-ng: info: [5500] successful run completed in 0.17s
rodsmith@
0
Clearly, the test failed -- it both reported an error and completed in a (reported) 0.17 seconds rather than the requested 60 seconds. The return code, though, was 0, indicating success.
The system on which I encountered this problem reports errors in this test >50% of the time, so I can easily test any code changes.
Changed in stress-ng: | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Colin Ian King (colin-king) |
Changed in stress-ng: | |
status: | In Progress → Fix Committed |
Changed in stress-ng: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
==30870== Syscall param mincore(vec) points to unaddressable byte(s) template. S:81) malloc. c:218) repos/stress- ng/stress- ng) valgrind/ vgpreload_ memcheck- x86-linux. so) malloc. c:218) repos/stress- ng/stress- ng)
==30870== at 0x41EB9E9: mincore (syscall-
==30870== by 0x808CE10: mincore_touch_pages (mincore.c:61)
==30870== by 0x806C457: stress_malloc (stress-
==30870== by 0x80FC404: stress_run (in /home/king/
==30870== by 0x804F279: main (stress-ng.c:3115)
==30870== Address 0x45fd29b is 0 bytes after a block of size 11 alloc'd
==30870== at 0x402E0D8: calloc (in /usr/lib/
==30870== by 0x808CDF9: mincore_touch_pages (mincore.c:57)
==30870== by 0x806C457: stress_malloc (stress-
==30870== by 0x80FC404: stress_run (in /home/king/
==30870== by 0x804F279: main (stress-ng.c:3115)
==30870==