qemu: Fix CVE-2022-4144
PATCH 1/1 qemu: Fix CVE-2022-4144
Add patch to fix CVE-2022-4144
--- meta/recipes-devtools/qemu/qemu.inc | 1 + .../qemu/qemu/CVE-2022-4144.patch | 99 +++++++++++++++++++ 2 files changed, 100 insertions(+) create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2022-4144.patch
meta/recipes-devtools/qemu/qemu.inc +1 -0
@@ -92,6 +92,7 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \ file://0020-target-ppc-move-xs-n-madd-am-ds-p-xs-n-msub-am-ds-p-.patch \ file://0021-target-ppc-implement-xs-n-maddqp-o-xs-n-msubqp-o.patch \ file://CVE-2022-3165.patch \ + file://CVE-2022-4144.patch \ " UPSTREAM_CHECK_REGEX = "qemu-(?P<pver>\d+(\.\d+)+)\.tar"
meta/recipes-devtools/qemu/qemu/CVE-2022-4144.patch new file +99 -0
99 lines not on this page · raw message
Signature · 1 line
2.17.1
Hi Bhabu (I hope I got your first name right)
Quoted 5 lines · BINDU
Add patch to fix CVE-2022-4144
Signed-off-by Bhabu Bindu <[email protected]>
Many thanks for the patch!
However, it is sent with an incomplete identity.
If I apply your patch through "git am", the author of the commit will be:
BINDU <[email protected]>
instead of
Bhabu Bindu <[email protected]>
Because of this issue, the maintainer has to manually fix this field when accepting your patch. Worse, if he doesn't catch this, that's harder to fix afterwards.
You should be able to fix this by running:
git config --global sendemail.from "[email protected]"
This should add a "From" field to the sent patch which "git am" should be able to match with your name. See https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded#Sending_using_git-send-email
Could you try to send an update (don't hesitate to send a private one to me first)?
Thanks in advance. This makes life easier for our very busy maintainers. Michael.
Signature · 3 lines
Michael Opdenacker, Bootlin Embedded Linux and Kernel engineering https://bootlin.com