blob: bfe8e2b1ea4a0cd09b7974f34d2150198077a154 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<think>
Alright, I need to classify this bug report into one of three categories: instruction, syscall, or runtime. Let me go through it step by step.
The bug report mentions that in Linux-user mode, QEMU doesn't check whether a page is PROT_EXEC before translating. It only verifies if the page is readable, which isn't sufficient because PROT_EXEC means the page can be executed. The issue could lead to problems where pages are treated as executable when they shouldn't be.
Looking at the categories:
- Instruction: This would involve issues with specific CPU instructions. But here, the problem is about memory permissions, not instruction handling.
- Syscall: It's about system calls. The report doesn't mention any syscall errors directly; it's more about how memory pages are checked during translation.
- Runtime: Errors that occur at runtime when executing code. This seems to fit because the issue affects how pages are handled dynamically as they're being executed, which happens at runtime.
So, the bug relates to the handling of memory permissions during execution, making it a runtime error.
</think>
runtime
|