Skip to content
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.

Sign up for GitHub

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

Jump to bottom

OpenSK panic in corpus testing (tracking) #177

Open
mingxguo27 opened this issue Oct 6, 2020 · 2 comments
Open

OpenSK panic in corpus testing (tracking) #177

mingxguo27 opened this issue Oct 6, 2020 · 2 comments
Assignees
@kaczmarczyck
Labels
tracking List of things to do

Comments

@mingxguo27
Copy link
Contributor

mingxguo27 commented Oct 6, 2020 •
edited
Loading

  1. Track kernel panic: some inputs in the corpus generated by the gray-box fuzzer caused a kernel crash when tested on hardware.
  2. OpenSK's main currently has 5 explicit panics (at L57, L96, L134, L209 and L353/355), consider keeping/changing the behaviour for fuzzing sake.
@mingxguo27 mingxguo27 changed the title OpenSK panic in corpus testing OpenSK panic in corpus testing (tracking) Oct 6, 2020
@mingxguo27
Copy link
Contributor Author

How can I assign it to myself?

@mingxguo27
Copy link
Contributor Author

mingxguo27 commented Oct 7, 2020 •
edited
Loading

The input file that caused a crash can be found here.

@jmichelp jmichelp added the bug Something isn't working label Oct 7, 2020
This was referenced Apr 8, 2021
Merged
Merged
@jmichelp jmichelp added tracking List of things to do and removed bug Something isn't working labels Aug 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kaczmarczyck kaczmarczyck

Labels
tracking List of things to do
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jmichelp @kaczmarczyck @mingxguo27