Fuzzing documentation cleanup.
This fixes some links and obsolete information prior to including new
information on FUZZ_TEST.
Bug: 1494445
Change-Id: Idb62487fb7d1d8ef66a40b8ef2b30b069f26b450
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4966742
Reviewed-by: Pâris Meuleman <[email protected]>
Commit-Queue: Adrian Taylor <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1214688}
diff --git a/testing/libfuzzer/README.md b/testing/libfuzzer/README.md
index 9b3b62b..29fc8af 100644
--- a/testing/libfuzzer/README.md
+++ b/testing/libfuzzer/README.md
@@ -21,6 +21,10 @@
automatically discovered by buildbots, built with different fuzzing engines,
then uploaded to the distributed [ClusterFuzz] fuzzing system to run at scale.
+You should fuzz any code which absorbs inputs from untrusted sources, such
+as the web. If the code parses, decodes, or otherwise manipulates that input,
+it's an especially good idea to fuzz it.
+
Create your first fuzz target and submit it by stepping through our [Getting
Started Guide].
@@ -41,7 +45,6 @@
## Further Reading
* [LibFuzzer integration] with Chromium and ClusterFuzz.
-* [AFL integration] with Chromium and ClusterFuzz.
* [Detailed references] for other integration parts.
* Writing fuzzers for the [non-browser parts of Chrome OS].
* [Fuzzing browsertests] if you need to fuzz multiple Chrome subsystems.
@@ -57,8 +60,6 @@
* [ClusterFuzz Stats] for fuzz targets built with AddressSanitizer and
libFuzzer.
-[AFL]: http://lcamtuf.coredump.cx/afl/
-[AFL integration]: AFL_integration.md
[Blackbox fuzzing]: https://google.github.io/clusterfuzz/setting-up-fuzzing/blackbox-fuzzing/
[Bugs found in open-source projects]: http://llvm.org/docs/LibFuzzer.html#trophies
[Bugs found in PDFium]: https://bugs.chromium.org/p/pdfium/issues/list?can=1&q=libfuzzer&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary&cells=tiles
