blob: 1bad30b3091ce2e7e909c42c17987ac9fa6c631e (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
|
The issue involves the QEMU-aarch64 emulator failing to correctly handle memory tag mismatches when running the GCC testsuite's HWAddressSanitizer (HWASAN) tests. Specifically, when executing `bitfield-2.exe`, QEMU reports a segmentation fault (SEGV) instead of detecting and reporting a tag mismatch as expected by the test.
Upon analyzing the error message:
```
==21137==ERROR: HWAddressSanitizer: SEGV on unknown address 0x0000000000f0
==21137==The signal is caused by a UNKNOWN memory access.
```
It's evident that QEMU is not correctly propagating the tag mismatch information to HWASAN. The test expects an error message indicating a "tag-mismatch" at a specific address, but instead, it encounters a SEGV, which suggests an unhandled or improperly reported memory access issue.
The problem likely stems from how QEMU handles Memory Tagging Extension (MTE) tags for AArch64. MTE is designed to detect invalid memory accesses by tagging memory regions and checking tag consistency during loads and stores. If QEMU fails to correctly implement or report tag mismatches, it can lead to such errors.
To categorize this issue under the provided options:
1. **Instruction**: This would pertain to a specific faulty instruction executed by QEMU. However, the error here isn't due to an incorrect instruction but rather how memory accesses are being handled and reported.
2. **Syscall**: This category relates to errors during system calls. The issue at hand doesn't involve a syscall failure but rather runtime behavior related to memory access tagging.
3. **Runtime**: This encompasses other runtime errors not covered by instructions or syscalls. Since the problem occurs during program execution due to improper handling of memory tags, it fits under this category.
**Conclusion:** The issue is a runtime error in QEMU's handling of Memory Tagging Extension (MTE) for AArch64, leading to incorrect reporting of memory access errors.
</think>
runtime
|