blob: efe99fa40c3d4bba1121a1717ca5b2c386907c24 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
|
<think>
Okay, let's tackle this. The user says "linux-user does not check PROT_EXEC". Hmm, I need to figure out what category this falls into. The options are instruction, syscall, or runtime.
First, PROT_EXEC is a protection flag related to memory pages, specifically for execution permission. The linux-user component in QEMU is probably responsible for handling system calls when running Linux user-mode programs. So if it's not checking the PROT_EXEC flag, that might relate to how it handles memory protections during syscalls like mmap or mprotect.
Wait, the bug is about not checking a certain protection. If a program tries to mark memory as executable and QEMU isn't verifying that, this could be a problem in the syscall handling. Because when a program makes a syscall to modify memory protections, QEMU's linux-user part should check those flags. So this seems like a syscall-related issue.
But maybe it's a runtime error? Runtime errors are other issues that occur during execution. However, since the issue is specifically about not validating a syscall parameter (PROT_EXEC), it's more likely a syscall error. The instruction category is for faulty instructions, like if there's a wrong CPU instruction used. That doesn't seem to fit here. So I think the correct category is syscall.
</think>
syscall
|