Hello Stefano, Stefano Stabellini <sstabell...@kernel.org> writes:
> On Thu, 21 Nov 2024, Volodymyr Babchuk wrote: >> Hi Stefano, >> >> Stefano Stabellini <sstabell...@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 <sstabell...@kernel.org> writes: >> >> >> >> > On Tue, 19 Nov 2024, Volodymyr Babchuk wrote: >> >> >> Hi Stefano, >> >> >> >> >> >> Stefano Stabellini <sstabell...@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. > > Please see: > https://gitlab.com/xen-project/fuzzer/xen-fuzzer Thank you! > Before pushing the master of > https://github.com/xen-troops/xen-fuzzer-rs > to > https://gitlab.com/xen-project/fuzzer/xen-fuzzer, > we need to make > sure that an appropriate Open Source license is clearly specified for > the project either with a top level COPYING file, or with an SPDX tag on > top of each source file, or both. MIT is a good candidate as LibAFL is > dual licensed as MIT. Sure. I added COPYING with MIT license. -- WBR, Volodymyr
