docs: rewrite reproducing_crashes.md #5529
Open
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
Let's list all the possible ways of reproducing syzkaller crashes locally and keep the instructions of how to manually craft a reproducer at the bottom. Add information about the ktest tooling - now it also automates the reproduction of syzbot bugs. See the discussion at: https://groups.google.com/g/syzkaller/c/UTPrWcJfS8Q/m/K1YXz-f1AQAJ
a-nogikh
force-pushed
the
features/update-reproducing_crashes.md
branch
from
a86430d
to
3667c49
Compare
koverstreet
reviewed
Nov 22, 2024
| $ sudo ./root_image init | ||
| $ sudo ./root_image create | ||
| $ sudo apt-get install capnproto | ||
| $ cargo install --path /tmp/ktest |
There was a problem hiding this comment.
Cap'n proto, and building & installing the rust binaries, shouldn't be needed for running ktest locally - those are just for the CI.
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.
Let's list all the possible ways of reproducing syzkaller crashes locally and keep the instructions of how to manually craft a reproducer at the bottom.
Add information about the ktest tooling - now it also automates the reproduction of syzbot bugs. See the discussion at: https://groups.google.com/g/syzkaller/c/UTPrWcJfS8Q/m/K1YXz-f1AQAJ