blob: 7ef3640ab6f274a60cd9e41ddb0ca54959afd0ce (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
|
kernel: 0.782
device: 0.763
ppc: 0.706
vnc: 0.625
architecture: 0.586
network: 0.583
socket: 0.550
performance: 0.495
graphic: 0.485
peripherals: 0.465
PID: 0.464
risc-v: 0.416
arm: 0.393
VMM: 0.376
boot: 0.327
virtual: 0.314
i386: 0.313
semantic: 0.313
x86: 0.310
register: 0.281
permissions: 0.279
hypervisor: 0.253
TCG: 0.244
KVM: 0.242
debug: 0.229
mistranslation: 0.229
files: 0.228
user-level: 0.148
assembly: 0.059
Fix DMA MMIO reentrancy issues
Additional information:
List of `DMA reentrancy` issues (usually found by [fuzzer](https://gitlab.com/qemu-project/qemu/-/issues?label_name[]=Fuzzer)):
- #62 (AHCI)
- #84, #305, #552 (SCSI)
- #451, #1282 (SDHCI)
- #540 (xHCI)
- #541 (EHCI)
- #542 (HDA)
- #557 (pcnet)
- #782 (NVMe)
- [eepro100](https://lore.kernel.org/qemu-devel/20210218140629.373646-1-ppandit@redhat.com/)
- #827 (virtio-blk)
- #1171 (tulip)
- #1543 (e1000e)
- #1563 (lsi53c895a)
Usually coredump backtrace includes multiple calls to `access_with_adjusted_size()` from the Memory API.
|