Some new fuzz corpus for loadmempool harness added in PR#19259
Loadmempool fuzz corpus #18
pull rajarshimaitra wants to merge 1 commits into bitcoin-core:main from rajarshimaitra:loadmempool changing 4608 files +29 −0-
rajarshimaitra commented at 5:16 PM on June 25, 2020: none
-
Loadmempool fuzz corpus 2b8eb745d4
-
Crypt-iQ commented at 9:54 AM on July 11, 2020: contributor
I think you found a bug in github because there are 4608 changed files and the diff is +29, -0 so the counter might have overflowed. Do you have the ability to run
afl-cminon the files you have, then you can just get the smallest set of files that gives the same coverage. -
practicalswift commented at 10:12 PM on July 13, 2020: contributor
@Crypt-iQ I think the
+29 -0line numbers refer to text files only. Binary files are skipped in that calculation :)BTW, the merge of this PR depends on the merge of the PR https://github.com/bitcoin/bitcoin/pull/19259. Usually new seeds are added to this repo only after the corresponding fuzzer has been merged into Bitcoin Core
master.Before merging this seed PR I think it makes sense to run libFuzzer's
-merge=1 -use_value_profile=1to trim the corpus in this PR. That is the seed minimization technique we've used in the past and I think it makes sense to keep using it (instead of sayafl-cmin) so that we get a consistent measure of coverage over time :)Minimizing the corpus would be a matter of:
$ mkdir smaller-set-of-files-giving-the-same-coverage/ $ test/fuzz/validation_load_mempool \ -merge=1 \ -use_value_profile=1 \ smaller-set-of-files-giving-the-same-coverage/ \ all-4608-files-in-this-pr/ # Submit only the files in smaller-set-of-files-giving-the-same-coverage/ as part of this PR :) - maflcko force-pushed the base branch on Jan 22, 2021
- automatic_base_change_succeeded maflcko
-
maflcko commented at 6:04 PM on March 18, 2021: contributor
Are the inputs minimized already?
-
maflcko commented at 11:23 AM on April 9, 2021: contributor
Closing for now due to inactivity
- maflcko closed this on Apr 9, 2021