All of lore.kernel.org
 help / color / mirror / Atom feed
From: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Jan Beulich <jbeulich@suse.com>, Julien Grall <julien@xen.org>,
	Bertrand Marquis <bertrand.marquis@arm.com>,
	Michal Orzel <michal.orzel@amd.com>,
	Dario Faggioli <dfaggioli@suse.com>,
	Juergen Gross <jgross@suse.com>,
	George Dunlap <gwd@xenproject.org>
Subject: Re: [RFC PATCH] xen: add libafl-qemu fuzzer support
Date: Thu, 21 Nov 2024 23:15:10 +0000	[thread overview]
Message-ID: <871pz4kwle.fsf@epam.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2411201406060.3516911@ubuntu-linux-20-04-desktop> (Stefano Stabellini's message of "Wed, 20 Nov 2024 14:07:47 -0800	(PST)")

Hi Stefano,

Stefano Stabellini <sstabellini@kernel.org> writes:

> On Wed, 20 Nov 2024, Volodymyr Babchuk wrote:
>> Hi Stefano,
>> 
>> (sorry, hit wrong Reply-To option, re-sending for wider audience)
>> 
>> Stefano Stabellini <sstabellini@kernel.org> writes:
>> 
>> > On Tue, 19 Nov 2024, Volodymyr Babchuk wrote:
>> >> Hi Stefano,
>> >>
>> >> Stefano Stabellini <sstabellini@kernel.org> writes:
>> >>

[...]

>> >>
>> >> I was considering this as well. Problem is that fuzzing should be
>> >> running for a prolonged periods of time. There is no clear consensus on
>> >> "how long", but most widely accepted time period is 24 hours. So looks
>> >> like it should be something like "nightly build" task. Fuzzer code
>> >> needs to be extended to support some runtime restriction, because right
>> >> now it runs indefinitely, until user stops it.
>> >
>> > We can let it run for 48 hours continuously every weekend using the
>> > Gitlab runners
>> 
>> Great idea. Anyways, I need to add option to limit runtime to the fuzzer
>> and invent some method for reporting discovered crashes to the CI first.
>> 
>> >
>> >> I am certainly going to implement this, but this is a separate topic,
>> >> because it quires changes in the fuzzer app. Speaking on which... Right
>> >> now both fuzzer and test harness reside in our github repo, as you
>> >> noticed. I believe it is better to host it on xenbits as an official
>> >> part of the Xen Project.
>> >
>> > Yes we can create repos under gitlab.com/xen-project for this, maybe a
>> > new subgroup gitlab.com/xen-project/fuzzer
>> 
>> Good. Whom should I ask to do this?
>
> I created gitlab.com/xen-project/fuzzer as an empty group. What
> repositories do you need under it?

Right now it is only the fuzzer itself
(https://github.com/xen-troops/xen-fuzzer-rs). If we are going to use
XTF then we don't need additional repo for the the harness.

-- 
WBR, Volodymyr

  reply	other threads:[~2024-11-21 23:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14 22:46 [RFC PATCH] xen: add libafl-qemu fuzzer support Volodymyr Babchuk
2024-11-19  1:46 ` Stefano Stabellini
2024-11-19 15:16   ` Volodymyr Babchuk
2024-11-19 18:32     ` Andrew Cooper
2024-11-19 20:46       ` Volodymyr Babchuk
2024-11-19 23:23     ` Stefano Stabellini
2024-11-20  0:50       ` Volodymyr Babchuk
2024-11-20 22:07         ` Stefano Stabellini
2024-11-21 23:15           ` Volodymyr Babchuk [this message]
2024-11-22  0:37             ` Stefano Stabellini
2024-11-25 23:23               ` Volodymyr Babchuk
2024-11-20  1:20     ` Marek Marczykowski-Górecki
2024-11-20 22:05       ` Stefano Stabellini
2024-11-19 18:02   ` Andrew Cooper

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=871pz4kwle.fsf@epam.com \
    --to=volodymyr_babchuk@epam.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=bertrand.marquis@arm.com \
    --cc=dfaggioli@suse.com \
    --cc=gwd@xenproject.org \
    --cc=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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 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.