blob: a5b82b037d34f9cb55d3fad4604e65fc8ffbea84 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, I need to classify this QEMU bug as either a user-mode or system-mode issue. Let's look at the details.
The problem occurs when executing an "int" instruction, specifically int 8. This is done through inline assembly in a C program. The test case provided doesn't require any special permissions and can be run by any unprivileged user.
QEMU is crashing with a kernel null pointer dereference error on Linux and a BSOD on Windows. Since the crash involves the host kernel, it suggests that the issue affects the system level rather than just user applications.
The fact that KVM isn't affected but TCG (the software emulator) is indicates it's specific to QEMU's emulation mode. This points towards issues in how QEMU handles interrupts or exceptions at a low level, which are typically part of the system-mode operations.
Also, the kernel panic log shows an Oops, which is a critical error in the Linux kernel, further supporting that this is a system-level issue.
So, putting it all together: executing a simple int instruction leads to a host kernel crash. This affects the entire system rather than just user processes, making it a system-mode bug.
</think>
system
|