qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kostiantyn Kostiuk <kkostiuk@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael Roth" <michael.roth@amd.com>,
	qemu-trivial@nongnu.org,
	"Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH v2] qga: Fix ubsan warning
Date: Wed, 30 Jul 2025 11:28:55 +0300	[thread overview]
Message-ID: <CAPMcbCp6cDWnV4PLnyYO5+rGoSeFEPSvGAOyJjK4N8r5Zkdv_w@mail.gmail.com> (raw)
In-Reply-To: <20250730072709.27077-1-thuth@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2247 bytes --]

Reviewed-by: Kostiantyn Kostiuk <kkostiuk@redhat.com>

@Thomas Huth <thuth@redhat.com> Is this fix critical to merge during code
freeze?

On Wed, Jul 30, 2025 at 10:27 AM Thomas Huth <thuth@redhat.com> wrote:

> From: Thomas Huth <thuth@redhat.com>
>
> When compiling QEMU with --enable-ubsan there is a undefined behavior
> warning when running "make check":
>
>  .../qga/commands-linux.c:452:15: runtime error: applying non-zero offset
> 5 to null pointer
>  #0 0x55ea7b89450c in build_guest_fsinfo_for_pci_dev
> ..../qga/commands-linux.c:452:15
>
> Fix it by avoiding the additional pointer variable here and use an
> "offset" integer variable instead.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  v2: Use an integer offset variable instead for checking for a NULL pointer
>
>  qga/commands-linux.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/qga/commands-linux.c b/qga/commands-linux.c
> index 9e8a934b9a6..0c41eb97190 100644
> --- a/qga/commands-linux.c
> +++ b/qga/commands-linux.c
> @@ -400,10 +400,10 @@ static bool build_guest_fsinfo_for_pci_dev(char
> const *syspath,
>                                             Error **errp)
>  {
>      unsigned int pci[4], host, hosts[8], tgt[3];
> -    int i, nhosts = 0, pcilen;
> +    int i, offset, nhosts = 0, pcilen;
>      GuestPCIAddress *pciaddr = disk->pci_controller;
>      bool has_ata = false, has_host = false, has_tgt = false;
> -    char *p, *q, *driver = NULL;
> +    char *p, *driver = NULL;
>      bool ret = false;
>
>      p = strstr(syspath, "/devices/pci");
> @@ -445,13 +445,13 @@ static bool build_guest_fsinfo_for_pci_dev(char
> const *syspath,
>
>      p = strstr(syspath, "/ata");
>      if (p) {
> -        q = p + 4;
> +        offset = 4;
>          has_ata = true;
>      } else {
>          p = strstr(syspath, "/host");
> -        q = p + 5;
> +        offset = 5;
>      }
> -    if (p && sscanf(q, "%u", &host) == 1) {
> +    if (p && sscanf(p + offset, "%u", &host) == 1) {
>          has_host = true;
>          nhosts = build_hosts(syspath, p, has_ata, hosts,
>                               ARRAY_SIZE(hosts), errp);
> --
> 2.50.1
>
>

[-- Attachment #2: Type: text/html, Size: 3159 bytes --]

  reply	other threads:[~2025-07-30  8:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-30  7:27 [PATCH v2] qga: Fix ubsan warning Thomas Huth
2025-07-30  8:28 ` Kostiantyn Kostiuk [this message]
2025-07-30  8:58   ` Thomas Huth
2025-07-30 11:46 ` Daniel P. Berrangé
2025-08-05 18:26 ` Michael Tokarev

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=CAPMcbCp6cDWnV4PLnyYO5+rGoSeFEPSvGAOyJjK4N8r5Zkdv_w@mail.gmail.com \
    --to=kkostiuk@redhat.com \
    --cc=berrange@redhat.com \
    --cc=michael.roth@amd.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=thuth@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).