-
Notifications
You must be signed in to change notification settings - Fork 60
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
Found one, now what? #2
Comments
Oh, so it's as simple as running this on bare metal right?
and I got:
|
You could also have taken the input file and run "./driver -tv < filename" on bare metal or inside the emulated environment. There are some notes on debugging in the readme that comes with the linux fuzzer. This is the madvise flag that is being used:
It requires a capability in the original namespace that only the "real" root has. — |
What's actually interesting is the behavior of C program, so this:
It actually manages to damage the executable on disk, I can't run it anymore even after a reboot. So is this the case that it poisons page-cache somehow, and then that page gets written back to disk? |
Hey, sorry to be thick, but this is the first time I'm doing this ... So after 3 days of fuzzing 4.6.5, I got this single crash:
I can provide you with the crash input file also. Now, questions:
The text was updated successfully, but these errors were encountered: