blob: 9f9372355bf217b8ead87f710a35ca35b555525b (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<think>
Okay, I need to classify this bug report into one of the given categories: instruction, syscall, or runtime. The issue is that QEMU isn't supporting the memfd_create syscall, resulting in an error when a userspace application uses it.
First, looking at what each category entails:
- **Instruction**: This would involve issues with how instructions are handled by the CPU emulator in QEMU. For example, if a specific instruction causes a problem.
- **Syscall**: This relates to system calls that the guest OS makes which aren't properly handled by QEMU's user mode emulation.
- **Runtime**: Covers other runtime errors not related to instructions or syscalls.
The bug report mentions that memfd_create is failing with an error "Unsupported syscall: 319". The number 319 corresponds to the syscall number for memfd_create in Linux. Since this is a system call issue where QEMU doesn't support it, the problem falls under the syscall category.
So, the classification should be 'syscall' because it's about handling a specific system call that isn't implemented.
</think>
The bug report describes an issue with QEMU not supporting the memfd_create syscall, which is a system call error.
sys
|