1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
|
<think>
Okay, I need to classify this bug report into one of the given categories for QEMU. Let me read through the problem description carefully.
The user mentioned that Golang binaries fail to start under linux-user mode in QEMU. They provided a stack trace and explained that it's due to the Go runtime not passing the CLONE_SYSVMEM flag during cloning. This causes some checks to fail, which is why their patch fixes the issue.
Looking at the categories: mistranslation, assembly lowering, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor, other.
This bug is related to how QEMU handles user-mode binaries and their interaction with system calls. The issue arises from missing flags in the clone operation when running Golang programs. Since this affects the runtime environment for binaries under user mode, it's more about how the emulation handles system calls and flags rather than a direct translation error.
The problem isn't specifically about assembly lowering or mistranslation of source code to target architecture. It's deeper into how QEMU emulates certain system functions that Golang relies on, particularly when starting new OS threads. This falls under the broader area of kernel emulation in user-mode environments.
Considering the categories, 'kernel' seems appropriate because it relates to how QEMU handles system calls and flags that are part of the operating system's kernel functionality within user mode.
</think>
The bug is related to how QEMU emulates certain system calls for Golang binaries. The failure occurs due to missing flags in the clone operation during runtime, affecting the kernel-level handling of OS threads.
**Answer:**
kernel
|