Add optional tmpfs storage for fuzzing corpus#461
Merged
Conversation
hbrodin
requested review from
michaelbrownuc,
ret2libc and
reytchison
as code owners
reytchison
reviewed
Jan 30, 2026
reytchison
reviewed
Jan 30, 2026
Add support for storing the node-local fuzzing corpus in tmpfs (RAM-based filesystem) for improved I/O performance during fuzzing operations. Key changes: - Add CORPUS_TMPFS_PATH environment variable to configure tmpfs location - Add cross-filesystem safe operations (copy+delete fallback for EXDEV) - Update Corpus class to use tmpfs path when enabled while maintaining correct remote path calculation for rsync synchronization - Add Helm chart configuration using /dev/shm (requires no host setup) - Update fuzzer-bot, coverage-bot, merger-bot, seed-gen deployments The feature is disabled by default. Enable by setting global.volumes.corpusTmpfs.enabled=true in values.yaml. Uses hostPath to /dev/shm/buttercup-corpus which is available on all Linux systems without requiring any Kubernetes host configuration.
hbrodin
force-pushed
the
feature/tmpfs-corpus
branch
from
dc6b5f9 to
3aa830c
Compare
reytchison
reviewed
Jan 30, 2026
reytchison
reviewed
Jan 30, 2026
reytchison
reviewed
Jan 30, 2026
reytchison
reviewed
Jan 30, 2026
- Add assertion that source is a file in hash_corpus before shutil.move - Remove unused move_file_cross_fs function from node_local - Remove duplicate tests for move_file_cross_fs from test files
reytchison
approved these changes
Feb 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add support for storing the node-local fuzzing corpus in tmpfs (RAM-based filesystem) for improved I/O performance during fuzzing operations.
Key changes:
The feature is disabled by default. Enable by setting global.volumes.corpusTmpfs.enabled=true in values.yaml.
Uses hostPath to /dev/shm/buttercup-corpus which is available on Linux systems without requiring any Kubernetes host configuration.