Internships/ProjectIdeas/QtestOssFuzz: Difference between revisions
m (edited project description and added a little more information) |
|||
Line 1: | Line 1: | ||
=== virtio-net oss-fuzz support === | === virtio-net oss-fuzz support === | ||
'''Status:''' Alexander Oleinik is working on this project for GSoC. | |||
'''Summary:''' Integrate oss-fuzz into QEMU so that the virtio-blk device can be fuzz tested. | '''Summary:''' Integrate oss-fuzz into QEMU so that the virtio-blk device can be fuzz tested. | ||
Line 22: | Line 23: | ||
* Skill level: intermediate | * Skill level: intermediate | ||
* Language: C | * Language: C | ||
* Mentor: Bandan Das <bsd@redhat.com> ("bsd" on #qemu IRC) | * Mentor: Bandan Das <bsd@redhat.com> ("bsd" on #qemu IRC), Paolo Bonzini <pbonzini@redhat.com> ("bonzini" on #qemu IRC), Stefan Hajnoczi <stefanha@redhat.com> ("stefanha" on #qemu IRC) |
Latest revision as of 15:15, 17 May 2019
virtio-net oss-fuzz support
Status: Alexander Oleinik is working on this project for GSoC.
Summary: Integrate oss-fuzz into QEMU so that the virtio-blk device can be fuzz tested.
oss-fuzz offers a fuzz testing service to open source projects. This means random inputs are continuously tested against the program in order to find crashes and other bugs. Fuzz testing complements hand-written test suites by exploring the input space of a program and therefore the code paths that may be taken.
The goal of this project is to experiment with integrating oss-fuzz into the virtio-net device that Qemu emulates for guest networking. virtio-net-pci is a PCI device connected to the virtual machine's PCI bus and has a configuration space that can be programmed by the guest. The device itself is specified by the VIRTIO specification which describes the functionality of the device. Bugs could potentially exist at both the PCI and VIRTIO levels, so it's important to fuzz both of them. Care should be taken to pick a design that could be generalized for all virtio devices, eg. virtio-blk.
Fuzzing emulated devices involves accessing their hardware registers randomly to make the device respond. QEMU has a device testing interface called "qtest" that accepts read/write and other commands over a socket and is ideal for writing device-level tests. You may find that oss-fuzz works better integrated directly into the QEMU program instead of as a separate qtest program, so you can consider adding a new command-line option to QEMU for running in oss-fuzz mode.
This project involves learning about VIRTIO and PCI devices, as well as figuring out how to integrate oss-fuzz into QEMU so that it can effective explore the code paths in virtio-net device emulation code. You will enjoy this project if you want to learn how device emulation works and are interested in fuzzers.
The project will primarily be in three phases. The first phase involves understanding the ecosytsem - Qemu, qtest, oss-fuzz and llvm etc. The second phase involves utilizing the qtest framework or utilizing the functionality to integrate in Qemu to fuzz the virtio-net device registers. THe third phase will involve running our fuzzing framework, analyzing results and identifying bugs.
Links:
Details:
- Skill level: intermediate
- Language: C
- Mentor: Bandan Das <bsd@redhat.com> ("bsd" on #qemu IRC), Paolo Bonzini <pbonzini@redhat.com> ("bonzini" on #qemu IRC), Stefan Hajnoczi <stefanha@redhat.com> ("stefanha" on #qemu IRC)