The SIGBUS occurs on the following actions:
[pid 196657] mmap(NULL, 268435456, PROT_READ|PROT_WRITE, MAP_SHARED, 4, 0) =
0x3ff78480000
[pid 196657] --- SIGBUS {si_signo=SIGBUS, si_code=BUS_ADRERR,
si_addr=0x3ff7f6ea000} ---
[pid 196657] +++ killed by SIGBUS +++
The mmap'ing was 0x3ff78480000 to 0x3ff78480000 + 268435456, e.g 0x3ff78480000
to 0x3ff88480000
The page that tiggered the SIGBUS was 0x3ff7f6ea000 which is between these
addresses, which shows it is a valid mapping.
The file based mapped file is basically a sparse file and gets populated
as the pages get touched, so a SIGBUS most probably occurs when we run
out of free blocks on disk, the kernel can't supply the page mapping and
we get a SIGBUS. I overlooked this corner case, so I'll work out a fix
for stress-ng.
** Changed in: stress-ng (Ubuntu)
Importance: Undecided => High
** Changed in: stress-ng (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569468
Title:
stress-ng mmap failing on zVM and LPAR
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1569468/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
