3 ms·

What? Greg's open-source work was maliciously attacked by the exact same actor who then submits incompetent patch requests. I think he responded in a totally ap

What? Greg's open-source work was maliciously attacked by the exact same actor who then submits incompetent patch requests. I think he responded in a totally appropriate manner. He does not owe these people anything - and certainly not kindness after their track record.

dcow 5y ago
It wasn't the same person and it wasn't an attack. Read the LWN article. > The writing of a paper on this research [PDF] was not the immediate cause of the recent events; instead, it was the posting of a buggy patch originating from an experimental static-analysis tool run by another developer at UMN. That led developers in the kernel community to suspect that the effort to submit intentionally malicious patches was still ongoing. Since then, it has become apparent that this is not the case, but by the time the full story became clear, the discussion was already running at full speed.
- tofuahdude 5y ago
  By "actor" I was referring to the institutionally untrustworthy UMN, but since you seem interested in splitting hairs, you should probably realize in doing so that Aditya Pakki === Aditya Pakki. Notice that Aditya is one of the signers of the apology letter: https://lore.kernel.org/lkml/CAK8KejpUVLxmqp026JY7x5GzHU2YJLPU8SzTZUNXU2OXC70ZQQ@mail.gmail.com/T/#u https://lore.kernel.org/lkml/CAK8KejpUVLxmqp026JY7x5GzHU2YJL... And that several of the identified vulnerabilities were tied to Aditya: https://lwn.net/ml/linux-kernel/YH+zwQgBBGUJdiVK@unreal/ https://lwn.net/ml/linux-kernel/YH+zwQgBBGUJdiVK@unreal/
  - re 5y ago
    Aditya's commits--though some were low-quality and/or buggy, including the one you linked--were not part of the intentionally deceptive "hypocrite commits" project.
  - seoaeu 5y ago
    UMN has many tens of thousands of students and faculty, on a similar scale to say Mountain View. It isn't "splitting hairs" to distinguish between the actual people involved in the untrustworthy behavior and everyone else.

dcow 5y ago

It wasn't the same person and it wasn't an attack. Read the LWN article. > The writing of a paper on this research [PDF] was not the immediate cause of the recent events; instead, it was the posting of a buggy patch originating from an experimental static-analysis tool run by another developer at UMN. That led developers in the kernel community to suspect that the effort to submit intentionally malicious patches was still ongoing. Since then, it has become apparent that this is not the case, but by the time the full story became clear, the discussion was already running at full speed.

tofuahdude 5y ago
By "actor" I was referring to the institutionally untrustworthy UMN, but since you seem interested in splitting hairs, you should probably realize in doing so that Aditya Pakki === Aditya Pakki. Notice that Aditya is one of the signers of the apology letter: https://lore.kernel.org/lkml/CAK8KejpUVLxmqp026JY7x5GzHU2YJLPU8SzTZUNXU2OXC70ZQQ@mail.gmail.com/T/#u https://lore.kernel.org/lkml/CAK8KejpUVLxmqp026JY7x5GzHU2YJL... And that several of the identified vulnerabilities were tied to Aditya: https://lwn.net/ml/linux-kernel/YH+zwQgBBGUJdiVK@unreal/ https://lwn.net/ml/linux-kernel/YH+zwQgBBGUJdiVK@unreal/
- re 5y ago
  Aditya's commits--though some were low-quality and/or buggy, including the one you linked--were not part of the intentionally deceptive "hypocrite commits" project.
- seoaeu 5y ago
  UMN has many tens of thousands of students and faculty, on a similar scale to say Mountain View. It isn't "splitting hairs" to distinguish between the actual people involved in the untrustworthy behavior and everyone else.