From: Leon Romanovsky <email@example.com> To: "firstname.lastname@example.org" <email@example.com> Cc: Trond Myklebust <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org> Subject: Re: [PATCH] SUNRPC: Add a check for gss_release_msg Date: Wed, 21 Apr 2021 16:34:00 +0300 [thread overview] Message-ID: <YIApyFQNCBOgNkhU@unreal> (raw) In-Reply-To: <YIAmy0zgrQW/44Hz@kroah.com> On Wed, Apr 21, 2021 at 03:21:15PM +0200, email@example.com wrote: > On Wed, Apr 21, 2021 at 01:11:03PM +0000, Trond Myklebust wrote: > > On Wed, 2021-04-21 at 15:19 +0300, Leon Romanovsky wrote: > > > On Wed, Apr 21, 2021 at 11:58:08AM +0000, Shelat, Abhi wrote: > > > > > > > > > > > > > > They introduce kernel bugs on purpose. Yesterday, I took a > > > > > > > > look on 4 > > > > > > > > accepted patches from Aditya and 3 of them added various > > > > > > > > severity security > > > > > > > > "holes". > > > > > > > > > > > > > > All contributions by this group of people need to be > > > > > > > reverted, if they > > > > > > > have not been done so already, as what they are doing is > > > > > > > intentional > > > > > > > malicious behavior and is not acceptable and totally > > > > > > > unethical. I'll > > > > > > > look at it after lunch unless someone else wants to do it… > > > > > > > > > > > > > > <snip> > > > > > > > > Academic research should NOT waste the time of a community. > > > > > > > > If you believe this behavior deserves an escalation, you can > > > > contact the Institutional Review Board (firstname.lastname@example.org) at UMN to > > > > investigate whether this behavior was harmful; in particular, > > > > whether the research activity had an appropriate IRB review, and > > > > what safeguards prevent repeats in other communities. > > > > > > The huge advantage of being "community" is that we don't need to do > > > all > > > the above and waste our time to fill some bureaucratic forms with > > > unclear > > > timelines and results. > > > > > > Our solution to ignore all @umn.edu contributions is much more > > > reliable > > > to us who are suffering from these researchers. > > > > > > > <shrug>That's an easy thing to sidestep by just shifting to using a > > private email address.</shrug> > > If they just want to be jerks, yes. But they can't then use that type > of "hiding" to get away with claiming it was done for a University > research project as that's even more unethical than what they are doing > now. > > > There really is no alternative for maintainers other than to always be > > sceptical of patches submitted by people who are not known and trusted > > members of the community, and to scrutinise those patches with more > > care. > > Agreed, and when we notice things like this that were determined to be > bad, we have the ability to easily go back and rip the changes out and > we can slowly add them back if they are actually something we want to > do. > > Which is what I just did: > https://email@example.com/ Greg, Did you push your series to the public git? I would like to add you a couple of reverts. And do you have a list of not reverted commits? It will save us from doing same comparison of reverted/not reverted over and over. Thanks > > thanks, > > greg k-h
next prev parent reply other threads:[~2021-04-21 13:34 UTC|newest] Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-07 0:16 Aditya Pakki 2021-04-07 15:34 ` J. Bruce Fields 2021-04-08 15:01 ` Trond Myklebust 2021-04-08 15:24 ` Olga Kornievskaia 2021-04-08 16:02 ` Trond Myklebust 2021-04-20 7:15 ` Greg KH 2021-04-20 17:10 ` J. Bruce Fields 2021-04-21 5:10 ` Leon Romanovsky 2021-04-21 5:43 ` Greg KH 2021-04-21 6:08 ` Leon Romanovsky [not found] ` <CA+EnHHSw4X+ubOUNYP2zXNpu70G74NN1Sct2Zin6pRgq--TqhA@mail.gmail.com> 2021-04-21 8:15 ` Greg KH 2021-04-21 10:07 ` Sudip Mukherjee 2021-04-21 10:21 ` Greg KH 2021-04-21 11:58 ` Shelat, Abhi 2021-04-21 12:08 ` Greg KH 2021-04-21 12:19 ` Leon Romanovsky 2021-04-21 13:11 ` Trond Myklebust 2021-04-21 13:20 ` Leon Romanovsky 2021-04-21 13:42 ` Steven Rostedt 2021-04-21 13:21 ` gregkh 2021-04-21 13:34 ` Leon Romanovsky [this message] 2021-04-21 13:50 ` gregkh 2021-04-21 14:12 ` Leon Romanovsky 2021-04-21 18:50 ` Alexander Grund 2021-04-21 13:37 ` J. Bruce Fields 2021-04-21 13:49 ` Leon Romanovsky 2021-04-21 13:56 ` J. Bruce Fields 2021-04-22 19:39 ` J. Bruce Fields 2021-04-23 17:25 ` Leon Romanovsky 2021-04-23 18:07 ` J. Bruce Fields 2021-04-23 19:29 ` Leon Romanovsky 2021-04-23 21:48 ` J. Bruce Fields 2021-04-24 7:21 ` Leon Romanovsky 2021-04-24 18:34 ` Al Viro 2021-04-24 21:34 ` J. Bruce Fields 2021-04-25 0:41 ` Theodore Ts'o 2021-04-25 6:29 ` Greg KH [not found] ` <20210426133605.GD21222@fieldses.org> 2021-04-26 13:47 ` J. Bruce Fields 2021-04-22 8:10 ` Sudip Mukherjee 2021-04-22 8:27 ` Greg KH 2021-04-21 12:51 ` Anna Schumaker 2021-04-21 14:15 ` Leon Romanovsky 2021-04-21 15:48 ` Theodore Ts'o 2021-04-21 17:34 ` Mike Rapoport 2021-04-22 3:57 ` Leon Romanovsky 2021-04-21 22:52 ` Guenter Roeck [not found] <CAHr+ZK-ayy2vku9ovuSB4egtOxrPEKxCdVQN3nFqMK07+K5_8g@mail.gmail.com> 2021-04-21 19:49 ` Theodore Ts'o 2021-04-22 7:50 ` Eric Biggers 2021-04-21 20:27 Weikeng Chen
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=YIApyFQNCBOgNkhU@unreal \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] SUNRPC: Add a check for gss_release_msg' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).