qemu-aarch64 MTE fails to report tag mismatch
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QEMU |
New
|
Undecided
|
Unassigned |
Bug Description
Hi,
While running the GCC testsuite with qemu-6.0 as simulator, I noticed several errors in the hwasan testsuite (output pattern tests).
I am attaching:
bitfield-2.exe
ld-linux-
libc.so.6
libdl.so.2
libhwasan.so.0
libm.so.6
libpthread.so.0
librt.so.1
The testcase can be executed via:
qemu-aarch64 -L . bitfield-2.exe
it currently generates:
HWAddressSaniti
==21137==ERROR: HWAddressSanitizer: SEGV on unknown address 0x0000000000f0 (pc 0x00550084e318 bp 0x005f01650d00 sp 0x005f01650d00 T21137)
==21137==The signal is caused by a UNKNOWN memory access.
==21137==Hint: address points to the zero page.
#0 0x550084e318 in GetAccessInfo /home/christoph
#1 0x550084e318 in HwasanOnSIGTRAP /home/christoph
#2 0x550084e318 in __hwasan:
#3 0x5f01651fec (<unknown module>)
#4 0x550084b508 in __hwasan_load2 /home/christoph
#5 0x400768 in f /home/christoph
#6 0x4007d0 in main /home/christoph
#7 0x550124cee0 in __libc_start_main ../csu/
#8 0x400688 (/home/
HWAddressSanitizer can not provide additional info.
SUMMARY: HWAddressSanitizer: SEGV /home/christoph
==21146==ABORTING
while the testcase expects HWAddressSanitizer: tag-mismatch on address 0x.....
You missed including libstdc++.so.6.
I ran with whatever libstdc++ I had lying around.
With qemu head, this terminates with
~/qemu/ bld/qemu- aarch64 -L . ./bitfield-2.exe
*** stack smashing detected ***: terminated
qemu: uncaught target signal 6 (Aborted) - core dumped
Aborted
I suspect the relevant MTE portion of this bug report
to be a duplicate of a kasan bug, the fix for which did
not make 6.0, but has since been committed as 09641ef93112.