TapTap/FastSync
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Testing: fuzz targets exist but are never run — no CI integration #135

New Issue
Closed
opened 2026-07-21 16:26:50 +02:00 by TapTap · 0 comments
TapTap commented 2026-07-21 16:26:50 +02:00
Owner
Copy Link
Copy Source

The project has 6 fuzz targets in tests/fuzz/:

  • fuzz_chunk_deserialize.c
  • fuzz_compress_decompress.c
  • fuzz_delta_deserialize.c
  • fuzz_delta_signature_deserialize.c
  • fuzz_glob_match.c
  • fuzz_metadata_from_buf.c

However:

  1. The CI workflow only builds the fuzz targets but never runs them
  2. There is no cmake --build build-fuzz --target fuzz step that executes the fuzzers
  3. There is no fuzzing corpus checked into the repository
  4. No regression tests for previously-found fuzz crashes
  5. No OSS-Fuzz integration

Suggested improvements

  1. Add a CI job that runs each fuzz target for a short duration (e.g., 30 seconds each) to catch regressions
  2. Check in a minimal seed corpus for each fuzz target
  3. Add a CIFuzz GitHub Action or Gitea equivalent for regression fuzzing on PRs
  4. Consider OSS-Fuzz integration for continuous fuzzing
  5. Add coverage-guided fuzzing with -runs=N and -max_total_time=N flags

The build already works (cmake -B build-fuzz -S . -DENABLE_FUZZ=ON && cmake --build build-fuzz), just the run step is missing.

Labels: testing, security, fuzzing, ci

The project has **6 fuzz targets** in `tests/fuzz/`: - `fuzz_chunk_deserialize.c` - `fuzz_compress_decompress.c` - `fuzz_delta_deserialize.c` - `fuzz_delta_signature_deserialize.c` - `fuzz_glob_match.c` - `fuzz_metadata_from_buf.c` However: 1. The CI workflow only **builds** the fuzz targets but never runs them 2. There is no `cmake --build build-fuzz --target fuzz` step that executes the fuzzers 3. There is no fuzzing corpus checked into the repository 4. No regression tests for previously-found fuzz crashes 5. No OSS-Fuzz integration ## Suggested improvements 1. Add a CI job that runs each fuzz target for a short duration (e.g., 30 seconds each) to catch regressions 2. Check in a minimal seed corpus for each fuzz target 3. Add a CIFuzz GitHub Action or Gitea equivalent for regression fuzzing on PRs 4. Consider OSS-Fuzz integration for continuous fuzzing 5. Add coverage-guided fuzzing with `-runs=N` and `-max_total_time=N` flags The build already works (`cmake -B build-fuzz -S . -DENABLE_FUZZ=ON && cmake --build build-fuzz`), just the run step is missing. **Labels**: testing, security, fuzzing, ci
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Defect or bug
 enhancement
Feature or improvement
 memory
Memory safety issue
 needs-triage
Needs human review
 performance
Performance issue
 quality
Code quality improvement
 security
Security vulnerability
 threading
Threading or concurrency
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
TapTap
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: TapTap/FastSync#135
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?