-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add basic options and documentations for fuzzing #1601
Merged
Merged
Conversation
This file contains 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
danobi
reviewed
Nov 10, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the detailed write up!
This option lets the program stop right after the specified process. The supported arguments are either 'semantic' or 'codegen'. For example, `bpftrace --test semantic -e 'BEGIN{}'` does semantic analysis and then quits. This option is useful for tests and fuzzing. This option is intended for developers, and its usage is not included in the reference guide.
danobi
reviewed
Nov 10, 2020
This visitor calls a callback function on each node.
When doing fuzzing, it is important to limit the number of AST nodes because otherwise a fuzzer might keep to generate a very long program that cause a stack overflow. This introduces `BPFTRACE_NODE_MAX` environment variable, and it controls the maximum number of AST nodes. This feature is intended for developers, and its usage is not included in the reference guide.
danobi
approved these changes
Nov 10, 2020
fbs
approved these changes
Nov 10, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice
Maybe we can try https://github.com/google/oss-fuzz too |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Several months ago and the last month, I fuzzed bftrace with AFL and found several bugs. This PR adds the documentation about it and some options useful for fuzzing. There are many fuzzers other than AFL and several techniques. I've been trying to fuzz various ways in my spare time and find some useful ways. I plan to update the document later. Also, I hope for more people to try to fuzz and find bugs and make bpftrace safer :)
Please read each commit messages and docs/fuzzing.md for the details.
Checklist
docs/reference_guide.md
CHANGELOG.md