From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>,
ltp@lists.linux.it, Nicolai Stange <nstange@suse.de>
Subject: Re: [LTP] [PATCH v2 2/7] Add test for CVE 2021-3656
Date: Fri, 26 May 2023 16:14:45 +0200 [thread overview]
Message-ID: <20230526141445.GB810612@pevik> (raw)
In-Reply-To: <20230526141001.GA810612@pevik>
> Hi Martin,
> FYI used toolchain [1]:
> clang version 7.0.1-8+deb10u2 (tags/RELEASE_701/final)
> Target: x86_64-pc-linux-gnu
FYI it's oldstable. Debian 12 Bookworm is planned to be released on 10 June,
in two weeks this error vanishes from the CI (we don't test oldoldstable).
Kind regards,
Petr
> Kind regards,
> Petr
> [1] https://github.com/pevik/ltp/actions/runs/5091551272/jobs/9151721119
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-05-26 14:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 13:34 [LTP] [PATCH v2 0/7] Two AMD SVM vulnerability tests Martin Doucha
2023-05-26 13:34 ` [LTP] [PATCH v2 1/7] KVM: Add VMSAVE/VMLOAD intercept constants Martin Doucha
2023-05-26 13:34 ` [LTP] [PATCH v2 2/7] Add test for CVE 2021-3656 Martin Doucha
2023-05-26 14:07 ` Petr Vorel
2023-05-26 14:10 ` Petr Vorel
2023-05-26 14:14 ` Petr Vorel [this message]
2023-05-26 14:27 ` Petr Vorel
2023-05-26 13:34 ` [LTP] [PATCH v2 3/7] lib: Add safe functions for pthread_kill() and mutexes Martin Doucha
2023-05-26 13:34 ` [LTP] [PATCH v2 4/7] KVM: Add async communication helper functions Martin Doucha
2023-05-29 5:51 ` Petr Vorel
2023-05-29 8:20 ` Martin Doucha
2023-05-29 8:27 ` Petr Vorel
2023-05-26 13:34 ` [LTP] [PATCH v2 5/7] KVM: Allow expected KVM_RUN errors in tst_kvm_run_instance() Martin Doucha
2023-05-26 13:34 ` [LTP] [PATCH v2 6/7] KVM: Add STGI/CLGI intercept constants Martin Doucha
2023-05-29 5:24 ` Petr Vorel
2023-05-26 13:34 ` [LTP] [PATCH v2 7/7] Add KVM test for CPU lockup through malicous SVM guest Martin Doucha
2023-05-29 10:02 ` [LTP] [PATCH v2 0/7] Two AMD SVM vulnerability tests Cyril Hrubis
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=20230526141445.GB810612@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
--cc=nstange@suse.de \
/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).