qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Darren Kenny <darren.kenny@oracle.com>
To: Alexander Bulekov <alxndr@bu.edu>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Bandan Das <bsd@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Thomas Huth <thuth@redhat.com>, Qiuhao Li <Qiuhao.Li@outlook.com>
Subject: Re: [PATCH] fuzz: only use generic-fuzz targets on oss-fuzz
Date: Wed, 22 Jun 2022 17:38:17 +0100	[thread overview]
Message-ID: <m2pmj0k612.fsf@oracle.com> (raw)
In-Reply-To: <20220622162635.eacnjindlfolsoqe@mozz.bu.edu>

On Wednesday, 2022-06-22 at 12:28:40 -04, Alexander Bulekov wrote:
> On 220622 1703, Darren Kenny wrote:
>> Hi Alex,
>> 
>> This looks good to me, so:
>> 
>> Reviewed-by: Darren Kenny <darren.kenny@oracle.com>
>> 
>> But, if it is at all possible to use Bash glob in a '[[ ... ]]' test
>> such as:
>> 
>>   if [[ $target == generic-fuzz-* ]]; then
>> 
>> that might read better - but it seems the default is that we don't
>> assume that, or am I wrong? (This is probably a question for others on
>> the CC-list)
>
> That sounds good to me. Should we change the script to #!/bin/bash, to
> be safe?

If it is acceptable to use the '[[ ... ]]' syntax then you'd definitely
want to ensure that it is bash that is used.

Thanks,

Darren.

> -Alex
>
>> 
>> Thanks,
>> 
>> Darren.
>> 
>> On Wednesday, 2022-06-22 at 11:50:28 -04, Alexander Bulekov wrote:
>> > The non-generic-fuzz targets often time-out, or run out of memory.
>> > Additionally, they create unreproducible bug-reports. It is possible
>> > that this is resulting in failing coverage-reports on OSS-Fuzz. In the
>> > future, these test-cases should be fixed, or removed.
>> >
>> > Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
>> > ---
>> >  scripts/oss-fuzz/build.sh | 2 +-
>> >  1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/scripts/oss-fuzz/build.sh b/scripts/oss-fuzz/build.sh
>> > index 98b56e0521..d8b4446d24 100755
>> > --- a/scripts/oss-fuzz/build.sh
>> > +++ b/scripts/oss-fuzz/build.sh
>> > @@ -105,7 +105,7 @@ do
>> >      # to be configured. We have some generic-fuzz-{pc-q35, floppy, ...} targets
>> >      # that are thin wrappers around this target that set the required
>> >      # environment variables according to predefined configs.
>> > -    if [ "$target" != "generic-fuzz" ]; then
>> > +    if echo "$target" | grep -q "generic-fuzz-"; then
>> >          ln  $base_copy \
>> >              "$DEST_DIR/qemu-fuzz-i386-target-$target"
>> >      fi
>> > -- 
>> > 2.27.0


  reply	other threads:[~2022-06-22 16:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 15:50 [PATCH] fuzz: only use generic-fuzz targets on oss-fuzz Alexander Bulekov
2022-06-22 16:03 ` Darren Kenny
2022-06-22 16:28   ` Alexander Bulekov
2022-06-22 16:38     ` Darren Kenny [this message]
2022-06-23  6:14       ` Thomas Huth

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=m2pmj0k612.fsf@oracle.com \
    --to=darren.kenny@oracle.com \
    --cc=Qiuhao.Li@outlook.com \
    --cc=alxndr@bu.edu \
    --cc=bsd@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).