From: Richard Palethorpe <rpalethorpe@suse.de>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/2] Add test for CVE 2021-38198
Date: Thu, 17 Mar 2022 07:35:51 +0000 [thread overview]
Message-ID: <874k3x58nw.fsf@suse.de> (raw)
In-Reply-To: <dd1485f7-1f0d-3360-451f-99656b0fbe9d@suse.cz>
Hello Martin,
Martin Doucha <mdoucha@suse.cz> writes:
> On 15. 03. 22 16:44, Richard Palethorpe wrote:
>> Martin Doucha <mdoucha@suse.cz> writes:
>>> So somebody will have to revert the fix and run the test on
>>> custom kernel to answer that question.
>>
>> Did you reproduce the bug?
>>
>> I could try this next week.
>
> Yes, I've verified the reproducer on older SLE-12SP5 and SLE-15SP3
> kernels. But none of them currently have the tdp_mmu sysfile so the test
> had to use the Intel/AMD KVM module reload fallback.
I see, in that case I don't think it's important to check it.
--
Thank you,
Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-03-17 7:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 16:49 [LTP] [PATCH 1/2] KVM test infrastructure Martin Doucha
2022-03-09 16:49 ` [LTP] [PATCH 2/2] Add test for CVE 2021-38198 Martin Doucha
2022-03-15 14:19 ` Richard Palethorpe
2022-03-15 15:04 ` Martin Doucha
2022-03-15 15:44 ` Richard Palethorpe
2022-03-15 16:14 ` Martin Doucha
2022-03-17 7:35 ` Richard Palethorpe [this message]
2022-03-17 11:55 ` Martin Doucha
2022-03-09 19:13 ` [LTP] [PATCH 1/2] KVM test infrastructure Petr Vorel
2022-03-10 14:10 ` Martin Doucha
2022-03-10 20:41 ` Petr Vorel
2022-03-15 15:00 ` Richard Palethorpe
2022-03-16 17:03 ` Martin Doucha
2022-03-17 7:59 ` Richard Palethorpe
2022-03-17 8:16 ` Li Wang
2022-03-17 10:42 ` Richard Palethorpe
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=874k3x58nw.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
/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