blob: 2373ee918a2025a6fef03383a4b02a8499869732 (
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
|
device: 0.838
graphic: 0.790
network: 0.765
ppc: 0.731
TCG: 0.730
files: 0.700
vnc: 0.634
socket: 0.610
architecture: 0.575
register: 0.573
VMM: 0.556
PID: 0.547
risc-v: 0.506
debug: 0.473
mistranslation: 0.471
semantic: 0.431
boot: 0.425
permissions: 0.405
i386: 0.400
x86: 0.364
arm: 0.350
kernel: 0.326
virtual: 0.312
performance: 0.223
user-level: 0.203
hypervisor: 0.189
assembly: 0.160
peripherals: 0.121
KVM: 0.070
Potential memory leak in virtio-crytpto
Description of problem:
There is a potential memory leak while using virtio-crypto with vhost-user backend.
The problem is due to misuse of error_setg in [backends/cryptodev-vhost-user.c#L284](https://gitlab.com/qemu-project/qemu/-/blob/master/backends/cryptodev-vhost-user.c#L284). After invoking error_setg(&local_error, ...), current procedure should not return without freeing err object pointed by local_error.
The same problem occured in cryptodev-builtin, which has been discussed in #2283 and fixed in f6abce29cc4afa0445cb3b29a265a114ac9fa744. The same fixes should be applied to cryptodev-vhost-user.
|