tests: Use BasicTestingSetup to initialise fuzzing environment #19074

pull practicalswift wants to merge 3 commits into bitcoin:master from practicalswift:fuzzers-2020-05-26 changing 20 files +38 −71

practicalswift commented at 8:58 PM on May 26, 2020: contributor

Use BasicTestingSetup to initialise fuzzing environment (as suggested by MarcoFalke).

Also: Remove unreachable fuzzing code. Various small coverage improvements.

See doc/fuzzing.md for information on how to fuzz Bitcoin Core. Don't forget to contribute any coverage increasing inputs you find to the Bitcoin Core fuzzing corpus repo.

Happy fuzzing :)
DrahtBot added the label Tests on May 26, 2020
practicalswift commented at 9:35 AM on June 2, 2020: contributor

~~Added commit: "tests: Avoid fuzzer-specific nullptr dereference in libevent when handling PROXY requests".~~
MarcoFalke commented at 11:16 AM on June 2, 2020: member

That commit seems unrelated. Mind splitting it up so that the libevent reviewers can review it?
practicalswift cross-referenced this on Jun 2, 2020 from issue tests: Avoid fuzzer-specific nullptr dereference in libevent when handling PROXY requests by practicalswift
practicalswift force-pushed on Jun 2, 2020
practicalswift commented at 11:57 AM on June 2, 2020: contributor

@MarcoFalke Done!
DrahtBot added the label Needs rebase on Jun 8, 2020
practicalswift force-pushed on Jun 8, 2020
DrahtBot removed the label Needs rebase on Jun 8, 2020
DrahtBot cross-referenced this on Jun 9, 2020 from issue net: Add regression fuzz harness for CVE-2017-18350. Add FuzzedSocket. by practicalswift
DrahtBot cross-referenced this on Jun 9, 2020 from issue tests: Add fuzzing harnesses for CAutoFile, CBufferedFile, LoadExternalBlockFile and other FILE* consumers by practicalswift
DrahtBot commented at 2:02 AM on June 9, 2020: contributor



The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.



Conflicts

No conflicts as of last run.
DrahtBot cross-referenced this on Jun 9, 2020 from issue tests: Add fuzzing harness for BanMan by practicalswift
DrahtBot cross-referenced this on Jun 11, 2020 from issue tests: Add fuzzing harness for {Read,Write}{LE,BE}{16,32,64} (crypto/common.h) by practicalswift
DrahtBot added the label Needs rebase on Jun 11, 2020
practicalswift force-pushed on Jun 11, 2020
DrahtBot removed the label Needs rebase on Jun 11, 2020
DrahtBot cross-referenced this on Jun 13, 2020 from issue fuzz: Add fuzzing harness for LoadMempool(...) and DumpMempool(...) by practicalswift
DrahtBot cross-referenced this on Jun 30, 2020 from issue net: Make DNS lookup mockable, add fuzzing harness by practicalswift
MarcoFalke referenced this in commit 505b4eda55 on Jul 10, 2020
DrahtBot added the label Needs rebase on Jul 11, 2020
tests: Use BasicTestingSetup to initialize fuzzing environment 096c69caf7
tests: Remove unreachable fuzzing code. Various small coverage improvements. ae05f0dfea
tests: Add InitializeFuzzingContext() for easy initialization of fuzzing context without debug logging (avoids writing to disk) e2b85985d2
practicalswift force-pushed on Jul 11, 2020
sidhujag referenced this in commit 8c57f3df6f on Jul 11, 2020
DrahtBot removed the label Needs rebase on Jul 11, 2020
practicalswift commented at 2:01 PM on August 11, 2020: contributor

@MarcoFalke I think you requested something along the lines of this PR at one time: do we want to proceed with this or should I close? :)
practicalswift closed this on Aug 26, 2020
practicalswift deleted the branch on Apr 10, 2021
PastaPastaPasta referenced this in commit e008b546e3 on Jul 17, 2022
bitcoin locked this on Aug 18, 2022

Contributors

Labels

Linked (view graph)

#19140 tests: Avoid fuzzer-specific nullptr dereference in libevent when handling PROXY requests

tests: Use BasicTestingSetup to initialise fuzzing environment #19074

Conflicts