blob: bd0ae74021f5c3414c9def8764f8cfdc5da5e5c3 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
<think>
Okay, so I need to classify this bug report about QEMU into one of three categories: instruction, syscall, or runtime. Let's break it down step by step.
The bug report mentions that when using `getsockopt` on `SO_RCVTIMEO_NEW` and `SO_SNDTIMEO_NEW`, an unexpected `int` is written. I remember that `getsockopt` is a system call used in socket programming to get various socket options. So this seems related to how the system handles these specific socket options.
Looking at the categories:
- "instruction" would relate to issues with specific CPU instructions, which doesn't seem relevant here.
- "syscall" deals with errors occurring during system calls, which fits because `getsockopt` is a syscall and there's an issue with it.
- "runtime" covers other runtime errors, but since this specifically mentions a syscall, it's more precise.
So the bug is likely related to how QEMU handles these socket options via syscalls. Therefore, the category should be 'syscall'.
</think>
The bug involves issues with system calls (`getsockopt`), so the appropriate category is:
**syscall**
Answer:
syscall
|