[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v3 1/2] Add libfuzzer target to fuzz/x86_instruction_emulator


  • To: Jan Beulich <jbeulich@xxxxxxxx>
  • From: Tamas K Lengyel <tamas@xxxxxxxxxxxxx>
  • Date: Mon, 22 Jul 2024 09:51:33 -0400
  • Arc-authentication-results: i=1; mx.zohomail.com; dkim=pass header.i=tklengyel.com; spf=pass smtp.mailfrom=tamas@xxxxxxxxxxxxx; dmarc=pass header.from=<tamas@xxxxxxxxxxxxx>
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1721656330; h=Content-Type:Content-Transfer-Encoding:Cc:Cc:Date:Date:From:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:Subject:To:To:Message-Id:Reply-To; bh=UWyLZ+rbKDcHujQTg+aeEEMLPQh3LsNe/noT9Sjxsf4=; b=PoVTfsdclnStztFqkziTDWf24HYVtE+Xa9vXkQjInvlyyRohU+Z+hrsBmn+gxa8HFE5NYqYE2x1P4M3DkWYwiQS2gbC7jg6xY6Hc/wfMkY2k9IHMERLYx5D14Ncx5093ZOPnKCiSa6MONysEghGQfYXSFqYH55RxiTo1WpAb/m0=
  • Arc-seal: i=1; a=rsa-sha256; t=1721656330; cv=none; d=zohomail.com; s=zohoarc; b=O579i6ruDriWBCMmmQcV0hHLn2ZQAfxwlu+8KLl0YcXg6uf74ee0/mbxBRL+MUwvS578jm6G6bvKqWgWMbCl+KZ8MiTcCgVK4lLb8YtUjRYtR0a4Q9HPoKpI+MpQomSRPrBsrjUiGS4EtV/rUxg2e/Buv+7yMSf3ZEn8F5FoZAI=
  • Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, Anthony PERARD <anthony@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 22 Jul 2024 13:52:17 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On Mon, Jul 22, 2024 at 8:24 AM Jan Beulich <jbeulich@xxxxxxxx> wrote:
>
> On 22.07.2024 13:27, Tamas K Lengyel wrote:
> > This target enables integration into oss-fuzz. Changing invalid input return
> > to -1 as values other then 0/-1 are reserved by libfuzzer. Also adding the
> > missing __wrap_vsnprintf wrapper which is required for successful oss-fuzz
> > build.
> >
> > Signed-off-by: Tamas K Lengyel <tamas@xxxxxxxxxxxxx>
> > ---
> > v3: don't include libfuzzer-harness in target 'all' as it requires specific 
> > cc
>
> With this, how is it going to be built at all? Only by invoking the special
> target "manually" as it seems? Which sets this up for easy bit-rotting. I
> wonder what others think here ...

Yes, by calling make with the specific target. It's not going to
bitrot because oss-fuzz will pick up any regression on a daily basis
to this target. I assume you would be interested in receiving the
fuzzing reports so it would show as a build failure in case something
broke it.

Tamas



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.