6 ms·
I don't suppose those long-running stress tests can be automated in any way, can they?
by darau1 4y ago
I don't suppose those long-running stress tests can be automated in any way, can they?
- hannob 4y agoThey are. There's a project by google called syzcaller, which pretty much does that (it's a bit more intelligent than that, and also includes running sanitizers, which find otherwise hard to detect memory safety and concurrency issues). It's actually causing an unexpected problem: It finds so many issues that kernel devs have troule keeping up fixing them.
- galangalalgol 4y agoExcellent! I keep complaining after each vuln pops up here that there isn't anyone with a kernel pipeline. Hopefully they have some static analysis too? Does the data out of this effort support the ggp that most of these defects are concurrency related vs the norm of memory safety?
- vincnetas 4y agoSo it turns out kernel does have unit tests, just that they are running after release.
- haspok 4y agoNo, this is way above the unit test level. Fuzzers usually are.
- FivenSeven 4y agoThey are. Many many companies run tests against the various kernel trees/branches, and will flood you with emails if you break the build. I can't remember who (I think IBM maybe?), but Greg KH said one company made a fantastic test suite out of nowhere. If you submit six patches, it will try each one, tell you what you broke in patch 3, and recommend a way you can fix it. And this just gets emailed to the person who submitted the patches, and the maintainers if they actually merged it. He said it was insanely advanced, and was made without the knowledge of the kernel maintainers. A company just made it and started sending emails one day.