diff options
author | Gaurav Gupta <gauragup@cisco.com> | 2023-03-30 12:51:43 -0700 |
---|---|---|
committer | Steve Sakoman <steve@sakoman.com> | 2023-04-19 04:32:59 -1000 |
commit | a526ef88ee960f6fce8ccae0230d5469309fd03a (patch) | |
tree | 01ec12421a94f42de9b524d6c4f1caf034fd8a84 /meta/recipes-devtools/qemu/qemu.inc | |
parent | 0c1e54eee110754633628a36b6564af9acdbf905 (diff) | |
download | poky-a526ef88ee960f6fce8ccae0230d5469309fd03a.tar.gz |
qemu: fix build error introduced by CVE-2021-3929 fix
The patch for CVE-2021-3929 applied on dunfell returns a value for a
void function. This results in the following compiler warning/error:
hw/block/nvme.c:77:6: error: void function
'nvme_addr_read' should not return a value [-Wreturn-type]
return NVME_DATA_TRAS_ERROR;
^ ~~~~~~~~~~~~~~~~~~~~
In newer versions of qemu, the functions is changed to have a return
value, but that is not present in the version of qemu used in “dunfell”.
Backport some of the patches to correct this.
(From OE-Core rev: 4ad98f0b27615ad59ae61110657cf69004c61ef4)
Signed-off-by: Gaurav Gupta <gauragup@cisco.com>
Signed-off-by: Gaurav Gupta <gauragup@cisco.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Diffstat (limited to 'meta/recipes-devtools/qemu/qemu.inc')
-rw-r--r-- | meta/recipes-devtools/qemu/qemu.inc | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/meta/recipes-devtools/qemu/qemu.inc b/meta/recipes-devtools/qemu/qemu.inc index 5466303c94..3b1bd3b656 100644 --- a/meta/recipes-devtools/qemu/qemu.inc +++ b/meta/recipes-devtools/qemu/qemu.inc | |||
@@ -115,6 +115,8 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \ | |||
115 | file://CVE-2021-3638.patch \ | 115 | file://CVE-2021-3638.patch \ |
116 | file://CVE-2021-20196.patch \ | 116 | file://CVE-2021-20196.patch \ |
117 | file://CVE-2021-3507.patch \ | 117 | file://CVE-2021-3507.patch \ |
118 | file://hw-block-nvme-refactor-nvme_addr_read.patch \ | ||
119 | file://hw-block-nvme-handle-dma-errors.patch \ | ||
118 | file://CVE-2021-3929.patch \ | 120 | file://CVE-2021-3929.patch \ |
119 | file://CVE-2022-4144.patch \ | 121 | file://CVE-2022-4144.patch \ |
120 | file://CVE-2020-15859.patch \ | 122 | file://CVE-2020-15859.patch \ |