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.
LinuxToday is a trusted, contributor-driven news resource supporting all types of Linux users. Our thriving international community engages with us through social media and frequent content contributions aimed at solving problems ranging from personal computing to enterprise-level IT operations. LinuxToday serves as a home for a community that struggles to find comparable information elsewhere on the web.
Advertiser Disclosure: Some of the products that appear on this site are from companies from which TechnologyAdvice receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. TechnologyAdvice does not include all companies or all types of products available in the marketplace.
