Conversation

Replying to and
yeah this is mostly that they sent a bunch of patches claiming to be fixing issues found by static analysis tools, implying that they knew what they were doing, and coming from a reasonably trustworthy source --> the patches got fairly little review
3
18
They've been regularly involved in submitting fixes based on static analysis. Not all of those patches are correct. Tools have many false positives and the students make mistakes. Do you have any evidence that this has to do with the study, which seemed to use gmail addresses?
2
They're students trying to silence errors from static analysis. It's a reach to claim that it's not in good faith because it's clearly wrong. They aren't experienced Linux kernel or probably even C developers. Many of the fixes they've submitted are still useful and correct.
2
If the Linux kernel cannot cope with that because it's too hard to review C code and determine if it's introducing a vulnerability or fixing one, then that's a serious problem. The study they did wasn't ethical but it wasn't malicious. They intended to stop the mistakes landing.
1
It's also completely wrong to frame it as if all the work done by the university was part of that small study. They didn't submit a bunch of patches as part of it. People are confusing the static analysis work with their attempt at demonstrating the review is flawed.
1
I mostly agree with you, though for a maintainer to be looking at a patch like the one I previously linked, having just dealt with the same people being malicious, I can fully understand Greg's response. I would agree that conclusions may have been jumped to.