Looks like I can trip this with any glibc version, using the attached
testcase.
Basically, this does an anoymous mmap, then a cacheflush on the address
returned from the mmap. We get an oops from the cacheflush on the actual
coprocessor instruction:
mcr p15, 0, r0, c7, c11, 1
- r0 is the start address given to cacheflush, and will be the address
which we see the invalid paging operation on.
I'm unsure why this instruction is generating an access to this address.
** Attachment added: "Testcase to trigger oops"
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/605042/+attachment/1848731/+files/test.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/605042
Title:
[armel] java fails to start with eglibc-2.12-0ubuntu4
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
