All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: gauragup@cisco.com
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Build error with dunfell release "yocto-3.1.24"
Date: Wed, 29 Mar 2023 11:03:16 -0700	[thread overview]
Message-ID: <CAMKF1sq0z7KDh1F243rKKCPr2x2thwvWrx68uw93spkx-2z1=w@mail.gmail.com> (raw)
In-Reply-To: <BYAPR11MB28862F6E6A1DFB11BFFB0FB9C2899@BYAPR11MB2886.namprd11.prod.outlook.com>

On Wed, Mar 29, 2023 at 9:51 AM Gaurav Gupta (gauragup) via
lists.openembedded.org <gauragup=cisco.com@lists.openembedded.org>
wrote:
>
> Hello,
>
>
>
> On latest “dunfell” branch, there’s a compiler warning/error when building QEMU.
>
>
>
> The patch for CVE-2021-3929 applied on dunfell returns a value for a void function: https://github.com/openembedded/openembedded-core/blob/dunfell/meta/recipes-devtools/qemu/qemu/CVE-2021-3929.patch#L58
>
>
>
> This results in the following warning/error:
>
>
>
> <ws>/qemu/4.2.0-r0/qemu-4.2.0/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”.
>
>

yeah perhaps we need to backport
https://github.com/qemu/qemu/commit/94cbcf530f9d9789b75ef1ae227ba4a4f702bf7d
as well.

https://github.com/openembedded/openembedded-core/blob/dunfell/meta/recipes-devtools/qemu/qemu/CVE-2021-3929.patch#L58

>
> Thanks,
>
> Gaurav
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#179292): https://lists.openembedded.org/g/openembedded-core/message/179292
> Mute This Topic: https://lists.openembedded.org/mt/97933015/1997914
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


  reply	other threads:[~2023-03-29 18:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BYAPR11MB28862F0807337647C5351586C2899@BYAPR11MB2886.namprd11.prod.outlook.com>
2023-03-29 16:51 ` Build error with dunfell release "yocto-3.1.24" Gaurav Gupta (gauragup)
2023-03-29 18:03   ` Khem Raj [this message]
2023-03-29 19:17     ` [OE-core] " Steve Sakoman
2023-03-29 23:47       ` Gaurav Gupta (gauragup)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMKF1sq0z7KDh1F243rKKCPr2x2thwvWrx68uw93spkx-2z1=w@mail.gmail.com' \
    --to=raj.khem@gmail.com \
    --cc=gauragup@cisco.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.