The regression found during testing is due to a small race between creating a file and expanding it's size using ftruncate the memory mapping of the data. In some cases, with slow backing store on slow devices and lack of sync'd data, the mapping will trip a SIGBUS because there is no file data to back the mapping. This issue has been in stress-ng for a while and has been found in the regression testing. This has been fixed, see https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1845011
The regression found during testing is due to a small race between creating a file and expanding it's size using ftruncate the memory mapping of the data. In some cases, with slow backing store on slow devices and lack of sync'd data, the mapping will trip a SIGBUS because there is no file data to back the mapping. This issue has been in stress-ng for a while and has been found in the regression testing. This has been fixed, see https:/ /bugs.launchpad .net/ubuntu/ +source/ stress- ng/+bug/ 1845011