blob: 17a314cf5d4ab6ba4f1d16d1b268651658c86e91 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
<think>
Okay, I need to classify this bug report as either user-mode or system-mode related. Let me read through the problem description carefully.
The issue is that when running qemu-s390x in user mode, it crashes with SIGILL when executing the "stck" instruction. The same instruction works fine in system mode. The reporter provided a minimal example where compiling and running the test program causes a crash under user mode but runs fine in system mode.
(SIGILL is an illegal instruction signal, which suggests that qemu isn't handling the stck instruction correctly in user mode.)
The problem affects software like ssh-keygen, which uses stck for entropy. The reporter also mentions that when they run qemu with various debug options, it produces a log trace showing where the issue occurs.
From this, I gather that the problem is specific to how qemu handles certain instructions in user mode versus system mode. User mode typically deals with executing application-level code without high privileges, while system mode involves handling higher-privilege operations and device interactions.
Since the crash happens only in user mode and the instruction works in system mode, this points to a bug in how qemu emulates the stck instruction when running applications (user space) rather than when it's acting as a full virtual machine with device emulation (system mode).
So, the classification should be 'user' because the problem occurs during execution of application code in user mode.
</think>
The issue is related to user-mode operation where the stck instruction isn't handled correctly.
user
|