From: Jan Beulich <jbeulich@suse.com>
To: Tamas K Lengyel <tamas@tklengyel.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Anthony PERARD <anthony@xenproject.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 2/2] Add tools/fuzz/oss-fuzz/build.sh
Date: Mon, 22 Jul 2024 14:20:21 +0200 [thread overview]
Message-ID: <9bd41e19-50f7-43e7-b3ce-c2870a836f79@suse.com> (raw)
In-Reply-To: <20240722112752.4981-2-tamas@tklengyel.com>
On 22.07.2024 13:27, Tamas K Lengyel wrote:
> --- /dev/null
> +++ b/LICENSES/Apache-2.0
> @@ -0,0 +1,202 @@
> +
> + Apache License
> + Version 2.0, January 2004
> + http://www.apache.org/licenses/
Better https:// (also near the end) nowadays?
Other files in this directory also have at least one Valid-License-Identifier:
line and at least one SPDX-URL: one. Depending on what would be put there, I'd
then wonder whether ...
> --- /dev/null
> +++ b/tools/fuzz/oss-fuzz/build.sh
> @@ -0,0 +1,11 @@
> +#!/bin/bash -eu
> +# Copyright 2024 Google LLC
> +# SPDX-License-Identifier: Apache-2.0
... there wouldn't want to be an "-only" tag here. Yet I'm entirely uncertain
with this, as CC-BY-4.0 also has no such tag.
I guess I should offer making respective adjustments while committing. I'll
wait with an ack though to give Alejandro some time to confirm that you
addressed his bash related comment.
Jan
> +# This script is intended to be run only from the oss-fuzz docker framework
> +# See https://google.github.io/oss-fuzz/getting-started/new-project-guide/#buildsh
> +cd xen
> +./configure --disable-stubdom --disable-pvshim --disable-docs --disable-xen --with-system-qemu
> +make clang=y -C tools/include
> +make clang=y -C tools/fuzz/x86_instruction_emulator libfuzzer-harness
> +cp tools/fuzz/x86_instruction_emulator/libfuzzer-harness $OUT/x86_instruction_emulator
next prev parent reply other threads:[~2024-07-22 12:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 11:27 [PATCH v3 1/2] Add libfuzzer target to fuzz/x86_instruction_emulator Tamas K Lengyel
2024-07-22 11:27 ` [PATCH v3 2/2] Add tools/fuzz/oss-fuzz/build.sh Tamas K Lengyel
2024-07-22 12:20 ` Jan Beulich [this message]
2024-07-22 13:49 ` Tamas K Lengyel
2024-07-22 14:03 ` Anthony PERARD
2024-07-22 12:24 ` [PATCH v3 1/2] Add libfuzzer target to fuzz/x86_instruction_emulator Jan Beulich
2024-07-22 13:51 ` Tamas K Lengyel
2024-07-22 13:57 ` Jan Beulich
2024-07-22 14:07 ` Tamas K Lengyel
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=9bd41e19-50f7-43e7-b3ce-c2870a836f79@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony@xenproject.org \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=tamas@tklengyel.com \
--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.