All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kautuk Consul <kautuk.consul.80@gmail.com>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] Open Question about KVM test-cases.
Date: Thu, 10 Feb 2022 19:00:20 +0530	[thread overview]
Message-ID: <CAKWYkK2HwzFNASKA0rotrytAh5KvKkZgiLLc4D9Y0eE+n7x+pg@mail.gmail.com> (raw)
In-Reply-To: <77bcf013-4ab3-5eb0-8a2c-9f346a5b1a77@suse.cz>


[-- Attachment #1.1: Type: text/plain, Size: 912 bytes --]

Thanks Martin. Will look into it.

On Thu, 10 Feb 2022, 18:30 Martin Doucha, <mdoucha@suse.cz> wrote:

> On 10. 02. 22 13:54, Cyril Hrubis wrote:
> > Hi!
> > Currently there are no tests for KVM in LTP, however Martin Doucha is
> > working on some CVE reproducers and send a RFC while ago (added to CC).
>
> You can find the RFC patch below. I've rewritten a large chunk of the
> code in the mean time and the example CVE reproducer doesn't actually
> work (the setup is incomplete so it passes even when it shouldn't) but
> I'm getting close to something that actually works. You can expect the
> first finished version before the end of the month.
>
>
> https://patchwork.ozlabs.org/project/ltp/patch/20220106165435.16556-1-mdoucha@suse.cz/
>
> --
> Martin Doucha   mdoucha@suse.cz
> QA Engineer for Software Maintenance
> SUSE LINUX, s.r.o.
> CORSO IIa
> Krizikova 148/34
> 186 00 Prague 8
> Czech Republic
>

[-- Attachment #1.2: Type: text/html, Size: 1475 bytes --]

[-- Attachment #2: Type: text/plain, Size: 60 bytes --]


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      reply	other threads:[~2022-02-10 13:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 11:33 [LTP] Open Question about KVM test-cases Kautuk Consul
2022-02-10 12:54 ` Cyril Hrubis
2022-02-10 13:00   ` Martin Doucha
2022-02-10 13:30     ` Kautuk Consul [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=CAKWYkK2HwzFNASKA0rotrytAh5KvKkZgiLLc4D9Y0eE+n7x+pg@mail.gmail.com \
    --to=kautuk.consul.80@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.