qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Nabih Estefan <nabihestefan@google.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	 qemu-devel@nongnu.org, pbonzini@redhat.com,  lvivier@redhat.com,
	 farosas@suse.de, sriram.yagnaraman@ericsson.com,
	 akihiko.odaki@daynix.com
Subject: Re: [PATCH v2] Running with `--enable-ubsan` leads to a qtest failure:
Date: Wed, 30 Apr 2025 18:06:08 +0100	[thread overview]
Message-ID: <87jz711svz.fsf@draig.linaro.org> (raw)
In-Reply-To: <CA+QoejXO3dJu-ifwaN1t9rK=M5RRBs9xaptE=ik6naz-3oMncQ@mail.gmail.com> (Nabih Estefan's message of "Wed, 30 Apr 2025 09:48:36 -0700")

Nabih Estefan <nabihestefan@google.com> writes:

> On Wed, Apr 30, 2025 at 5:03 AM Peter Maydell <peter.maydell@linaro.org> wrote:
>>
>> On Tue, 29 Apr 2025 at 16:56, Nabih Estefan <nabihestefan@google.com> wrote:
>> >
>> > v2: used ldl_le_p and lduw_l_p instead of memcpy as per upstream
>> > suggestion.
>> >
>> > ```
>> > ../tests/qtest/libqos/igb.c:106:5: runtime error: load of misaligned address 0x562040be8e33 for type 'uint32_t', which requires 4 byte alignment
>> > ```
>> > Instead of straight casting the uint8_t array, we use memcpy to assure
>> > alignment is correct against uint32_t and uint16_t.
>> >
>> > Signed-off-by: Nabih Estefan <nabihestefan@google.com>
>> > ---
>> >  tests/qtest/libqos/igb.c | 4 ++--
>> >  1 file changed, 2 insertions(+), 2 deletions(-)
>> >
>> > diff --git a/tests/qtest/libqos/igb.c b/tests/qtest/libqos/igb.c
>> > index f40c4ec4cd..2e0bb58617 100644
>> > --- a/tests/qtest/libqos/igb.c
>> > +++ b/tests/qtest/libqos/igb.c
>> > @@ -104,10 +104,10 @@ static void igb_pci_start_hw(QOSGraphObject *obj)
>> >      e1000e_macreg_write(&d->e1000e, E1000_RDT(0), 0);
>> >      e1000e_macreg_write(&d->e1000e, E1000_RDH(0), 0);
>> >      e1000e_macreg_write(&d->e1000e, E1000_RA,
>> > -                        le32_to_cpu(*(uint32_t *)address));
>> > +                        ldl_le_p((uint32_t *)address));
>> >      e1000e_macreg_write(&d->e1000e, E1000_RA + 4,
>> >                          E1000_RAH_AV | E1000_RAH_POOL_1 |
>> > -                        le16_to_cpu(*(uint16_t *)(address + 4)));
>> > +                        lduw_le_p((uint16_t *)(address + 4)));
>>
>> ldl_le_p() etc take a 'void *' -- the casts here should not be
>> necessary.
>
> Should I send a new patch to fix this if it's already been queued to
> testing/next?
> Or can it be fixed directly in that branch?

I'll fix it up, I've taken notes when I re-base.

>
> Thanks,
> Nabih
>
>>
>> thanks
>> -- PMM

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


      reply	other threads:[~2025-04-30 17:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-29 15:56 [PATCH v2] Running with `--enable-ubsan` leads to a qtest failure: Nabih Estefan
2025-04-30  2:48 ` Richard Henderson
2025-04-30  9:18 ` Laurent Vivier
2025-04-30 10:49 ` Alex Bennée
2025-04-30 12:31   ` Philippe Mathieu-Daudé
2025-04-30 12:03 ` Peter Maydell
2025-04-30 16:48   ` Nabih Estefan
2025-04-30 17:06     ` Alex Bennée [this message]

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=87jz711svz.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=akihiko.odaki@daynix.com \
    --cc=farosas@suse.de \
    --cc=lvivier@redhat.com \
    --cc=nabihestefan@google.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sriram.yagnaraman@ericsson.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).