Noob: How to use syzkaller to test device drivers?

176 views
Skip to first unread message

xulin Zhang

unread,
Oct 13, 2023, 8:43:12 AM10/13/23
to syzkaller
I've recently started working with syzkaller, and I've completed the basic tutorials. Now, I want to replicate an experiment from a research paper that used syzkaller to test several drivers, including tty, drm, sequencer, midi, vivid, and floppy. I believe I should use 'enable_syscalls' to target specific drivers, but I've encountered an issue. I'm getting the error in the screenshot when testing floppy.
c6cdd9d6dcc848379ab803fa07ace69.png
I use the syzlang description file provided by syzkaller, and the error appears to indicate that the '/dev/fd#' file is not being opened. it might require some configuration related to my Linux kernel?
Looking forward to your answers, thank you.
fuzz.cfg

Aleksandr Nogikh

unread,
Oct 13, 2023, 9:40:30 AM10/13/23
to xulin Zhang, syzkaller
In your case, syzkaller checked that none of the /dev/fd0, /dev/fd1 ... /dev/fd9 devices exists on the machine that you fuzz and disabled the syz_open_dev$floppy call, which transitively disabled all other calls you that you were trying to enable.

If you want to fuzz floppy, you need to ensure that at least one floppy device is available. If it's a qemu virtual machine, you could e.g. pass some image via the `-fda` argument.

FWIW note that Linux block developers are not particularly happy about bug reports for floppy: https://lore.kernel.org/all/7df3e30a-aa31-495c...@kernel.dk/ 

--
You received this message because you are subscribed to the Google Groups "syzkaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller/420fb90c-b15c-4be2-9a6d-f4f4488ec9bfn%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages