Advanced

Using syzkaller: fuzzing your changes

Posted by mfilion on · Post a comment
Collabora Blog; By Andre Almeida 		Mail this story
Print this story

In the second part of this series on syzkaller, we looked at how to install the tool and use it to improve our code base and detect programming bugs in the Linux kernel. Now, how does syzkaller report a bug it finds in the execution path of a system call? Let's add a new syscall description and see how it goes.

Full Story

  Nav
» Read more about: Groups: Developer, Kernel, Linux

» Get new stories by e-mail: nightly or as they are published

« Return to the newswire homepage

Comments

No comments yet. Be the first.

Post a comment

A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.

Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help

Sign up and post (it is free)  or  Log in and post