|
|
Log in / Subscribe / Register

Finding driver bugs with DR. CHECKER

Finding driver bugs with DR. CHECKER

Posted Sep 11, 2017 12:13 UTC (Mon) by gregkh (subscriber, #8)
In reply to: Finding driver bugs with DR. CHECKER by dc123
Parent article: Finding driver bugs with DR. CHECKER

Why not? It's a provable statement, see the numbers that Google has provided as to where the kernel crashes they get all come from (hint, it's not the core kernel, nor in the upstream driver code...)

So this is a good thing to work to help solve, which is why we run so many different code checking tools, to ignore the state of out-of-tree driver quality is to not work to solve a real problem.


to post comments

Finding driver bugs with DR. CHECKER

Posted Sep 12, 2017 2:19 UTC (Tue) by dc123 (guest, #117760) [Link] (1 responses)

I simply found it amusing that nobody bothered to proofread a paper about finding bugs :)

Finding driver bugs with DR. CHECKER

Posted Sep 12, 2017 14:10 UTC (Tue) by jerojasro (guest, #98169) [Link]

you know how it goes; you don't see the typos until it's printed.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds