From: Alexander Bulekov <alxndr@bu.edu>
To: Qiuhao Li <Qiuhao.Li@outlook.com>
Cc: thuth@redhat.com, qemu-devel@nongnu.org, darren.kenny@oracle.com,
bsd@redhat.com, stefanha@redhat.com, pbonzini@redhat.com
Subject: Re: [PATCH v4 2/7] fuzz: double the IOs to remove for every loop
Date: Wed, 6 Jan 2021 23:19:16 -0500 [thread overview]
Message-ID: <20210107041916.zy7xtzbbdurnowdc@mozz.bu.edu> (raw)
In-Reply-To: <ME3P282MB17455D5C7EBFF7D9D7510A4DFCD80@ME3P282MB1745.AUSP282.PROD.OUTLOOK.COM>
On 201229 1240, Qiuhao Li wrote:
> Instead of removing IO instructions one by one, we can try deleting multiple
> instructions at once. According to the locality of reference, we double the
> number of instructions to remove for the next round and recover it to one
> once we fail.
>
> This patch is usually significant for large input.
>
> Test with quadrupled trace input at:
> https://bugs.launchpad.net/qemu/+bug/1890333/comments/1
>
> Patched 1/6 version:
> real 0m45.904s
> user 0m16.874s
> sys 0m10.042s
>
> Refined version:
> real 0m11.412s
> user 0m6.888s
> sys 0m3.325s
>
> Signed-off-by: Qiuhao Li <Qiuhao.Li@outlook.com>
Reviewed-by: Alexander Bulekov <alxndr@bu.edu>
> ---
> scripts/oss-fuzz/minimize_qtest_trace.py | 33 +++++++++++++++---------
> 1 file changed, 21 insertions(+), 12 deletions(-)
>
> diff --git a/scripts/oss-fuzz/minimize_qtest_trace.py b/scripts/oss-fuzz/minimize_qtest_trace.py
> index aa69c7963e..0b665ae657 100755
> --- a/scripts/oss-fuzz/minimize_qtest_trace.py
> +++ b/scripts/oss-fuzz/minimize_qtest_trace.py
> @@ -85,19 +85,28 @@ def minimize_trace(inpath, outpath):
>
> i = 0
> newtrace = trace[:]
> - # For each line
> + remove_step = 1
> while i < len(newtrace):
> - # 1.) Try to remove it completely and reproduce the crash. If it works,
> - # we're done.
> - prior = newtrace[i]
> - print("Trying to remove {}".format(newtrace[i]))
> - # Try to remove the line completely
> - newtrace[i] = ""
> + # 1.) Try to remove lines completely and reproduce the crash.
> + # If it works, we're done.
> + if (i+remove_step) >= len(newtrace):
> + remove_step = 1
> + prior = newtrace[i:i+remove_step]
> + for j in range(i, i+remove_step):
> + newtrace[j] = ""
> + print("Removing {lines} ...".format(lines=prior))
> if check_if_trace_crashes(newtrace, outpath):
> - i += 1
> + i += remove_step
> + # Double the number of lines to remove for next round
> + remove_step *= 2
> continue
> - newtrace[i] = prior
> -
> + # Failed to remove multiple IOs, fast recovery
> + if remove_step > 1:
> + for j in range(i, i+remove_step):
> + newtrace[j] = prior[j-i]
> + remove_step = 1
> + continue
> + newtrace[i] = prior[0] # remove_step = 1
> # 2.) Try to replace write{bwlq} commands with a write addr, len
> # command. Since this can require swapping endianness, try both LE and
> # BE options. We do this, so we can "trim" the writes in (3)
> @@ -118,7 +127,7 @@ def minimize_trace(inpath, outpath):
> if(check_if_trace_crashes(newtrace, outpath)):
> break
> else:
> - newtrace[i] = prior
> + newtrace[i] = prior[0]
>
> # 3.) If it is a qtest write command: write addr len data, try to split
> # it into two separate write commands. If splitting the write down the
> @@ -151,7 +160,7 @@ def minimize_trace(inpath, outpath):
> if check_if_trace_crashes(newtrace, outpath):
> i -= 1
> else:
> - newtrace[i] = prior
> + newtrace[i] = prior[0]
> del newtrace[i+1]
> i += 1
> check_if_trace_crashes(newtrace, outpath)
> --
> 2.25.1
>
next prev parent reply other threads:[~2021-01-07 4:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 4:39 [PATCH v4 0/7] fuzz: improve crash case minimization Qiuhao Li
2020-12-29 4:40 ` [PATCH v4 1/7] fuzz: accelerate non-crash detection Qiuhao Li
2021-01-07 3:42 ` Alexander Bulekov
2021-01-07 4:18 ` Alexander Bulekov
2021-01-08 2:47 ` Qiuhao Li
2021-01-10 13:10 ` Qiuhao Li
2021-01-10 16:00 ` Alexander Bulekov
2021-01-11 2:19 ` Qiuhao Li
2020-12-29 4:40 ` [PATCH v4 2/7] fuzz: double the IOs to remove for every loop Qiuhao Li
2021-01-07 4:19 ` Alexander Bulekov [this message]
2020-12-29 4:40 ` [PATCH v4 3/7] fuzz: split write operand using binary approach Qiuhao Li
2021-01-07 4:28 ` Alexander Bulekov
2020-12-29 4:40 ` [PATCH v4 4/7] fuzz: loop the remove minimizer and refactoring Qiuhao Li
2021-01-07 4:53 ` Alexander Bulekov
2021-01-08 2:49 ` Qiuhao Li
2020-12-29 4:40 ` [PATCH v4 5/7] fuzz: set bits in operand of write/out to zero Qiuhao Li
2021-01-07 5:08 ` Alexander Bulekov
2020-12-29 4:40 ` [PATCH v4 6/7] fuzz: add minimization options Qiuhao Li
2021-01-07 5:54 ` Alexander Bulekov
2020-12-29 4:40 ` [PATCH v4 7/7] fuzz: heuristic split write based on past IOs Qiuhao Li
2021-01-08 4:30 ` Alexander Bulekov
2021-01-05 8:00 ` Ping: [PATCH v4 0/7] fuzz: improve crash case minimization Qiuhao Li
2021-01-08 4:32 ` Alexander Bulekov
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=20210107041916.zy7xtzbbdurnowdc@mozz.bu.edu \
--to=alxndr@bu.edu \
--cc=Qiuhao.Li@outlook.com \
--cc=bsd@redhat.com \
--cc=darren.kenny@oracle.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).