blob: 76ccb75a99dcd86dc154aca5f4fb66612f1012d4 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, I need to classify this bug report as either 'user-mode' or 'system-mode'. Let's start by understanding what each term means.
User-mode refers to software that runs in a non-privileged environment, where applications execute without direct access to hardware. This is the usual mode for most programs. System-mode, on the other hand, involves higher privileges and often interacts with hardware, peripherals, or core operating system components.
Looking at the bug report, it's about qemu-img convert sometimes creating corrupted images when the input isn't fully synced. The issue arises in userland tools like OpenStack Nova, but the root cause is in how QEMU uses fiemap without syncing.
The fix suggested involves modifying a flag in QEMU's code to use FIEMAP_FLAG_SYNC. This means it's about how the application interacts with file system calls and data handling, not involving kernel-level operations or hardware.
Since QEMU runs as a user-space application and the problem is within its file handling logic without needing kernel privileges or device access, this seems like a user-mode issue.
</think>
user
|