blob: 4723095c1c4e0f2ff18e0f3f9ddfdc591d10aee2 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, I need to classify this QEMU bug report as either user-mode or system-mode related. The problem is about the faccessat2 syscall not being implemented for the LoongArch64 architecture in QEMU's user mode.
The issue arises when running a simple bash script that checks if a file is readable. The script returns "ERROR" even though the file exists and is readable, which suggests that the system call handling is incorrect.
Looking at the strace logs, there's an unknown syscall 439, which corresponds to faccessat2. Since QEMU's user-mode emulation handles syscalls for emulated processes, the missing implementation of this syscall falls under user-mode issues.
System-mode issues typically involve higher-privilege operations like device drivers or OS-level functionalities. This problem doesn't seem to touch those areas but rather how user-space applications interact with system calls in QEMU's user emulator.
Therefore, the bug is related to user-mode.
</think>
user
|