fuzz: remove GetDescriptorChecksum from string harness
What the developer wrote
Authored by Bruno Garcia
fuzz: remove GetDescriptorChecksum from string harness
This function is already strongly fuzzed by other harness.
E.g: descriptor_parse calls it several times during parsing
and serialization. Also, calling GetDescriptorChecksum with
a string of length 32 is not effective to exercise it.
What changed, and why it matters
This commit removes one line from a fuzz test file. Fuzz tests are automated tools that feed random inputs to functions to find crashes or bugs. The change simply stops calling the GetDescriptorChecksum function in this particular test, because other fuzz tests already exercise it more thoroughly. There is no change to any production code, no bug fix, and no security-relevant behavior change in the Bitcoin Core software itself.
No action needed. This is a test-only cleanup with no security relevance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit removes a single invocation of GetDescriptorChecksum(random_string_1) from src/test/fuzz/string.cpp. The commit message explains the removal as cleanup/redundancy: the function is already heavily fuzzed by the descriptor_parse harness, and the string harness’s random 32-byte input is not an effective input shape for that function. The diff affects only test code; no implementation code is modified.
Changed components
src/test/fuzz/string.cppInspect captured patch +0 / −1
diff --git a/src/test/fuzz/string.cpp b/src/test/fuzz/string.cpp
index d3156336..b36ac297 100644
--- a/src/test/fuzz/string.cpp
+++ b/src/test/fuzz/string.cpp
@@ -63,7 +63,6 @@ FUZZ_TARGET(string)
const auto width{fuzzed_data_provider.ConsumeIntegralInRange<size_t>(1, 1000)};
(void)FormatParagraph(random_string_1, width, fuzzed_data_provider.ConsumeIntegralInRange<size_t>(0, width));
(void)FormatSubVersion(random_string_1, fuzzed_data_provider.ConsumeIntegral<int>(), random_string_vector);
- (void)GetDescriptorChecksum(random_string_1);
(void)HelpExampleCli(random_string_1, random_string_2);
(void)HelpExampleRpc(random_string_1, random_string_2);
(void)HelpMessageGroup(random_string_1);
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.