Here's Why University of Minnesota is Getting Banned From Contributing to Linux Kernel Code

It all started with a seemingly innocent patch to the Linux kernel on the 6th April, 2021. A Ph.D. candidate at University of Minnesota submitted this really small patch:

Since the patch was simple and seemed to improve the code quality, it got green light from a couple of members initially but then it got questioned by Eric Dumazet on 9th April.

It was on the 19th April when veteran kernel contributor Al Viro rebuked the contributor for submitting a “fix that does not fix anything”. And at this point, he points out two possibilities for such a garbage code submission:

Plainly put, the patch demonstrates either complete lack of understanding or somebody not acting in good faith. If it’s the latter[1], may I suggest the esteemed sociologists to fuck off and stop testing the reviewers with deliberately spewed excrements?

If you feel that he used too strong words, there is a reason and history behind that.

Stealthily introducing vulnerabilities in open source software via hypocrite commits

Well, that’s the title of a research paper submitted by Qiushi Wu (Ph.D. student), Kangjie Lu (assistant professor) of University of Minnesota.

The researchers were testing the feasibility of stealthily introducing vulnerabilities in OSS via hypocrite commits, i.e., seemingly beneficial commits that in fact introduce other critical issues.

And they chose the Linux kernel project to carry out their experiments.

Al Viro found that the ‘useless patch’ from Aditya Pakki was likely to be part of this research. Greg Kroah-Hartman (GKH), the second-in-command of the Kernel project after Linus Torvalds, advised not to waste the kernel maintainer’s time such patches.

Please stop submitting known-invalid patches. Your professor is playing around with the review process in order to achieve a paper in some strange and bizarre way.
This is not ok, it is wasting our time, and we will have to report this, AGAIN, to your university…

Apparently, that was not the only troublesome patch request. As Leon Romanovsky noted, there were 3 more such patches from the same researcher.

Greg kernel bad patch

Due to the public bashing, the university researcher tried to play victim and started to blame kernel maintainer’s attitude.

I respectfully ask you to cease and desist from making wild accusations that are bordering on slander.

These patches were sent as part of a new static analyzer that I wrote and it’s sensitivity is obviously not great. I sent patches on the hopes to get feedback. We are not experts in the linux kernel and repeatedly making these statements is disgusting to hear.

Obviously, it is a wrong step but your preconceived biases are so strong that you make allegations without merit nor give us any benefit of doubt.

I will not be sending any more patches due to the attitude that is not only unwelcome but also intimidating to newbies and non experts.

This irked Greg to the extent that he stated that he “will now have to ban all future contributions from your University and rip out your previous contributions, as they were obviously submitted in bad-faith with the intent to cause problems.”

Greg kernel main

Research and stuff is fine but it should not be at the expense of trolling busy people. That’s what I think.

I wonder how Linux Torvalds would have reacted to this patch!

About the author
Abhishek Prakash

Abhishek Prakash

Created It's FOSS 13 years ago to share my Linux adventures. Have a Master's degree in Engineering and years of IT industry experience. Huge fan of Agatha Christie detective mysteries πŸ•΅οΈβ€β™‚οΈ

Become a Better Linux User

With the FOSS Weekly Newsletter, you learn useful Linux tips, discover applications, explore new distros and stay updated with the latest from Linux world

itsfoss happy penguin

Great! You’ve successfully signed up.

Welcome back! You've successfully signed in.

You've successfully subscribed to It's FOSS.

Success! Check your email for magic link to sign-in.

Success! Your billing info has been updated.

Your billing was not updated.