| 2022-05-10 21:43:44 |
Michael Reed |
bug |
|
|
added bug |
| 2022-05-10 21:46:15 |
Michael Reed |
attachment added |
|
com.canonical.certification__memory_memory_stress_ng.stderr https://bugs.launchpad.net/stress-ng/+bug/1972906/+attachment/5588323/+files/com.canonical.certification__memory_memory_stress_ng.stderr |
|
| 2022-06-07 13:54:17 |
Jeff Lane |
bug watch added |
|
https://github.com/ColinIanKing/stress-ng/issues/201 |
|
| 2022-06-07 13:54:23 |
Jeff Lane |
stress-ng: status |
New |
Confirmed |
|
| 2022-10-19 08:55:46 |
Colin Ian King |
stress-ng: assignee |
|
Colin Ian King (colin-king) |
|
| 2022-10-19 08:55:49 |
Colin Ian King |
stress-ng: importance |
Undecided |
High |
|
| 2022-10-28 09:38:07 |
Colin Ian King |
description |
On 22.04 stress-ng --malloc appears to pass but gives the following error messages:
stress-ng: fail: [2903753] stress-ng-malloc: allocation at 0x5631fc61b530 does not contain correct value
stress-ng: fail: [2903853] stress-ng-malloc: allocation at 0x5631fcb17920 does not contain correct value
...
info: 5 failures reached, aborting stress process
...
stress-ng: fail: [2903814] stress-ng-malloc: allocation at 0x5631fc6a92e0 does not contain correct value
stress-ng: info: [2903729] successful run completed in 10.81s
Steps to recreate:
stress-ng --aggressive --verify --timeout 300 --malloc 0
This appears to be a regression as this error is not seen on 20.04 |
== SRU Jammy ==
== Justification ==
stress-ng --malloc 1 --verify verification incorrectly performs a page checksum on the wrong page and will incorrectly report a test failure when the data is perfectly correct.
== Fix ==
This was fixed with the upstream fix:
commit ddecc607f916f8c9561f40c7ddc7d9e5c7528ff1
Author: Mayuresh Chitale <mchitale@ventanamicro.com>
Date: Tue Jun 7 12:07:10 2022 +0530
stress-malloc: Fix for https://github.com/ColinIanKing/stress-ng/issues/201
After realloc is done the address of the allocated memory is not stashed to the
buffer like it is done after calloc/malloc. This causes the verify check
to fail as the buffer contains the stale address.
Signed-off-by: Mayuresh Chitale <mchitale@ventanamicro.com>
..this is the Kinetic release and works as expected. The fix is clean application of this patch.
== Regression Risk ==
This is a one line fix to store the correct checksum in the correct page. it only affects the one stress-ng stress case, namely the malloc stressor. The backport has been regression tested on Jammy for a 1hr run w/o seeing any regression. The change is also present in Kinetic and works perfectly. The regression risk is very small, this only change the behavior of the malloc test when using the --verify option. The modification is to memory that is mapped into the address space so there is no segmentation fault regression potential.
---------------------------------------------------------
On 22.04 stress-ng --malloc appears to pass but gives the following error messages:
stress-ng: fail: [2903753] stress-ng-malloc: allocation at 0x5631fc61b530 does not contain correct value
stress-ng: fail: [2903853] stress-ng-malloc: allocation at 0x5631fcb17920 does not contain correct value
...
info: 5 failures reached, aborting stress process
...
stress-ng: fail: [2903814] stress-ng-malloc: allocation at 0x5631fc6a92e0 does not contain correct value
stress-ng: info: [2903729] successful run completed in 10.81s
Steps to recreate:
stress-ng --aggressive --verify --timeout 300 --malloc 0
This appears to be a regression as this error is not seen on 20.04 |
|
| 2022-10-28 12:34:15 |
Colin Ian King |
bug |
|
|
added subscriber MOTU Stable Release Updates |
| 2022-10-28 18:26:21 |
Andreas Hasenack |
description |
== SRU Jammy ==
== Justification ==
stress-ng --malloc 1 --verify verification incorrectly performs a page checksum on the wrong page and will incorrectly report a test failure when the data is perfectly correct.
== Fix ==
This was fixed with the upstream fix:
commit ddecc607f916f8c9561f40c7ddc7d9e5c7528ff1
Author: Mayuresh Chitale <mchitale@ventanamicro.com>
Date: Tue Jun 7 12:07:10 2022 +0530
stress-malloc: Fix for https://github.com/ColinIanKing/stress-ng/issues/201
After realloc is done the address of the allocated memory is not stashed to the
buffer like it is done after calloc/malloc. This causes the verify check
to fail as the buffer contains the stale address.
Signed-off-by: Mayuresh Chitale <mchitale@ventanamicro.com>
..this is the Kinetic release and works as expected. The fix is clean application of this patch.
== Regression Risk ==
This is a one line fix to store the correct checksum in the correct page. it only affects the one stress-ng stress case, namely the malloc stressor. The backport has been regression tested on Jammy for a 1hr run w/o seeing any regression. The change is also present in Kinetic and works perfectly. The regression risk is very small, this only change the behavior of the malloc test when using the --verify option. The modification is to memory that is mapped into the address space so there is no segmentation fault regression potential.
---------------------------------------------------------
On 22.04 stress-ng --malloc appears to pass but gives the following error messages:
stress-ng: fail: [2903753] stress-ng-malloc: allocation at 0x5631fc61b530 does not contain correct value
stress-ng: fail: [2903853] stress-ng-malloc: allocation at 0x5631fcb17920 does not contain correct value
...
info: 5 failures reached, aborting stress process
...
stress-ng: fail: [2903814] stress-ng-malloc: allocation at 0x5631fc6a92e0 does not contain correct value
stress-ng: info: [2903729] successful run completed in 10.81s
Steps to recreate:
stress-ng --aggressive --verify --timeout 300 --malloc 0
This appears to be a regression as this error is not seen on 20.04 |
== SRU Jammy ==
== Justification ==
stress-ng --malloc 1 --verify verification incorrectly performs a page checksum on the wrong page and will incorrectly report a test failure when the data is perfectly correct.
== Fix ==
This was fixed with the upstream fix:
commit ddecc607f916f8c9561f40c7ddc7d9e5c7528ff1
Author: Mayuresh Chitale <mchitale@ventanamicro.com>
Date: Tue Jun 7 12:07:10 2022 +0530
stress-malloc: Fix for https://github.com/ColinIanKing/stress-ng/issues/201
After realloc is done the address of the allocated memory is not stashed to the
buffer like it is done after calloc/malloc. This causes the verify check
to fail as the buffer contains the stale address.
Signed-off-by: Mayuresh Chitale <mchitale@ventanamicro.com>
..this is the Kinetic release and works as expected. The fix is clean application of this patch.
== Test Case ==
Run:
stress-ng --aggressive --verify --timeout 300 --malloc 0
Without the fix, it will spit out errors like:
stress-ng: fail: [2060] stress-ng-malloc: allocation at 0x5590f0d68670 does not contain correct value
stress-ng: fail: [2060] stress-ng-malloc: allocation at 0x5590f0d68670 does not contain correct value
stress-ng: fail: [2059] stress-ng-malloc: allocation at 0x5590ea580830 does not contain correct value
== Regression Risk ==
This is a one line fix to store the correct checksum in the correct page. it only affects the one stress-ng stress case, namely the malloc stressor. The backport has been regression tested on Jammy for a 1hr run w/o seeing any regression. The change is also present in Kinetic and works perfectly. The regression risk is very small, this only change the behavior of the malloc test when using the --verify option. The modification is to memory that is mapped into the address space so there is no segmentation fault regression potential.
---------------------------------------------------------
On 22.04 stress-ng --malloc appears to pass but gives the following error messages:
stress-ng: fail: [2903753] stress-ng-malloc: allocation at 0x5631fc61b530 does not contain correct value
stress-ng: fail: [2903853] stress-ng-malloc: allocation at 0x5631fcb17920 does not contain correct value
...
info: 5 failures reached, aborting stress process
...
stress-ng: fail: [2903814] stress-ng-malloc: allocation at 0x5631fc6a92e0 does not contain correct value
stress-ng: info: [2903729] successful run completed in 10.81s
Steps to recreate:
stress-ng --aggressive --verify --timeout 300 --malloc 0
This appears to be a regression as this error is not seen on 20.04 |
|
| 2022-10-28 19:42:21 |
Andreas Hasenack |
stress-ng: status |
Confirmed |
Incomplete |
|
| 2022-10-28 19:42:24 |
Andreas Hasenack |
bug |
|
|
added subscriber Andreas Hasenack |
| 2022-10-29 14:16:59 |
Andreas Hasenack |
stress-ng: status |
Incomplete |
In Progress |
|
| 2022-10-29 14:27:16 |
Andreas Hasenack |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2022-10-29 14:27:18 |
Andreas Hasenack |
bug |
|
|
added subscriber SRU Verification |
| 2022-10-29 14:27:24 |
Andreas Hasenack |
tags |
|
verification-needed verification-needed-jammy |
|
| 2022-10-29 14:27:45 |
Andreas Hasenack |
bug task added |
|
stress-ng (Ubuntu) |
|
| 2022-10-29 14:27:55 |
Andreas Hasenack |
nominated for series |
|
Ubuntu Jammy |
|
| 2022-10-29 14:27:55 |
Andreas Hasenack |
bug task added |
|
stress-ng (Ubuntu Jammy) |
|
| 2022-10-29 14:28:12 |
Andreas Hasenack |
stress-ng (Ubuntu): status |
New |
Fix Released |
|
| 2022-10-29 14:28:19 |
Andreas Hasenack |
stress-ng (Ubuntu Jammy): status |
New |
In Progress |
|
| 2022-10-29 14:28:24 |
Andreas Hasenack |
stress-ng (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2023-02-28 10:38:57 |
Colin Ian King |
tags |
verification-needed verification-needed-jammy |
verification-done verification-done-jammy |
|
| 2023-03-01 03:14:08 |
Chris Halse Rogers |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2023-03-01 03:14:29 |
Launchpad Janitor |
stress-ng (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2023-03-01 10:24:57 |
Colin Ian King |
stress-ng: status |
In Progress |
Fix Released |
|
