From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, alxndr@bu.edu, laurent@vivier.eu
Subject: Re: [PATCH v2 0/6] esp: fix asserts/segfaults discovered by fuzzer
Date: Thu, 1 Apr 2021 08:56:54 +0100 [thread overview]
Message-ID: <6f91d44f-297a-72ef-bd47-198533f8a4eb@ilande.co.uk> (raw)
In-Reply-To: <d33de3a4-0ec6-0506-b19a-1e6043615980@redhat.com>
On 30/03/2021 10:59, Paolo Bonzini wrote:
> Hi,
>
> I also had some failures of the tests on CI, which is why I hadn't incorporated these
> changes yet. Thanks for the advance warning, I'll wait for your v3.
>
> Paolo
Hi Paolo,
I've just posted the latest v3 which passes all my local boot tests and the extra
test cases posted to LP. There is one failure on Gitlab CI but that is for the
clang-user build for tcg-tests-s390x-linux-user which is an existing issue.
Apologies it took a bit longer than expected: my laptop isn't the fastest in the
world and booting everything will full debug and ASAN across several targets is
tremendously slow :/
Also it seems there is something wrong with the qtest dependencies: for my current
build of ~2900 files, the final commit to add the qtest for am53c974 which adds the
test to test/qtest/meson.build causes ~2100 of those files to be rebuilt :(
ATB,
Mark.
prev parent reply other threads:[~2021-04-01 8:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 23:02 [PATCH v2 0/6] esp: fix asserts/segfaults discovered by fuzzer Mark Cave-Ayland
2021-03-17 23:02 ` [PATCH v2 1/6] esp: don't underflow cmdfifo if no message out/command data is present Mark Cave-Ayland
2021-03-17 23:58 ` Alexander Bulekov
2021-03-17 23:02 ` [PATCH v2 2/6] esp: don't overflow cmdfifo if TC is larger than the cmdfifo size Mark Cave-Ayland
2021-03-17 23:02 ` [PATCH v2 3/6] esp: ensure cmdfifo is not empty and current_dev is non-NULL Mark Cave-Ayland
2021-03-18 0:10 ` [PATCH v2 3/6] esp: ensure cmdfifo is not empty and current_dev is non-NULL\ Alexander Bulekov
2021-03-17 23:02 ` [PATCH v2 4/6] esp: don't underflow fifo when writing to the device Mark Cave-Ayland
2021-03-18 0:12 ` Alexander Bulekov
2021-03-17 23:02 ` [PATCH v2 5/6] esp: always check current_req is not NULL before use in DMA callbacks Mark Cave-Ayland
2021-03-18 0:12 ` Alexander Bulekov
2021-03-17 23:02 ` [PATCH v2 6/6] tests/qtest: add tests for am53c974 device Mark Cave-Ayland
2021-03-18 0:14 ` Alexander Bulekov
2021-03-18 12:10 ` Paolo Bonzini
2021-03-18 18:13 ` [PATCH v2 0/6] esp: fix asserts/segfaults discovered by fuzzer Paolo Bonzini
2021-03-30 7:34 ` Mark Cave-Ayland
2021-03-30 9:59 ` Paolo Bonzini
2021-04-01 7:56 ` Mark Cave-Ayland [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=6f91d44f-297a-72ef-bd47-198533f8a4eb@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=alxndr@bu.edu \
--cc=laurent@vivier.eu \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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 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).