[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YIAzfsMx6bn5Twu8@unreal>
Date: Wed, 21 Apr 2021 17:15:26 +0300
From: Leon Romanovsky <leon@...nel.org>
To: Anna Schumaker <anna.schumaker@...app.com>
Cc: "J. Bruce Fields" <bfields@...ldses.org>,
Greg KH <gregkh@...uxfoundation.org>,
Aditya Pakki <pakki001@....edu>,
Chuck Lever <chuck.lever@...cle.com>,
Trond Myklebust <trond.myklebust@...merspace.com>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Dave Wysochanski <dwysocha@...hat.com>,
Linux NFS Mailing List <linux-nfs@...r.kernel.org>,
netdev@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] SUNRPC: Add a check for gss_release_msg
On Wed, Apr 21, 2021 at 08:51:02AM -0400, Anna Schumaker wrote:
> On Wed, Apr 21, 2021 at 2:07 AM Leon Romanovsky <leon@...nel.org> wrote:
> >
> > On Tue, Apr 20, 2021 at 01:10:08PM -0400, J. Bruce Fields wrote:
> > > On Tue, Apr 20, 2021 at 09:15:23AM +0200, Greg KH wrote:
> > > > If you look at the code, this is impossible to have happen.
> > > >
> > > > 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...
> > >
> > > What's the story here?
> >
> > Those commits are part of the following research:
> > https://github.com/QiushiWu/QiushiWu.github.io/blob/main/papers/OpenSourceInsecurity.pdf
>
> This thread is the first I'm hearing about this. I wonder if there is
> a good way of alerting the entire kernel community (including those
> only subscribed to subsystem mailing lists) about what's going on? It
> seems like useful information to have to push back against these
> patches.
IMHO, kernel users ML is good enough for that.
Powered by blists - more mailing lists