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
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807732 Title: lots of "fail" and "error" messages in mmap test, yet test exits with a 0 code To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1807732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
