blob: dbdd59bcaed61f944730b7453a754dd803c80c74 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
|
<think>
Alright, let's try to figure out the category for this bug report. The user mentioned that when using read() with an mmap'ed address as the output buffer in QEMU's linux-user mode, it returns EFAULT instead of working as expected.
So, first, I'm thinking about what each category means. "mistranslation" is about incorrect mapping from source to target architecture. But this seems more like a permission issue with memory access.
Looking at other categories, "permissions" stands out because the problem is about read permissions being required where they shouldn't be. The code works on qemu-system-arm and natively but fails in user-mode QEMU, which suggests it's an issue with how QEMU handles memory permissions when emulating.
I don't see issues related to assembly lowering ("assembly"), hypervisor, or other areas like graphics or network. It's specifically about read vs write access on mmap'ed memory, so "permissions" fits best.
</think>
permissions
|