[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170514055848.GA23149@lst.de>
Date: Sun, 14 May 2017 07:58:48 +0200
From: Christoph Hellwig <hch@....de>
To: davem@...emloft.net
Cc: Bart Van Assche <Bart.VanAssche@...disk.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
"ubraun@...ux.vnet.ibm.com" <ubraun@...ux.vnet.ibm.com>
Subject: Re: [PATCH] net/smc: mark as BROKEN due to remote memory exposure
Dave,
this patch has not been superceeded by anything, can you explain why it
has been marked as such in patchworks?
On Thu, May 11, 2017 at 02:57:43PM +0000, Bart Van Assche wrote:
> On Wed, 2017-05-10 at 09:26 +0200, Christoph Hellwig wrote:
> > The driver has a lot of quality issues due to the lack of RDMA-side
> > review, and explicitly bypasses APIs to register all memory once a
> > connection is made, and thus allows remote access to memoery.
> >
> > Mark it as broken until at least that part is fixed.
>
> Since this is the only way to get the BROKEN marker in the v4.11 stable
> kernel series:
>
> Acked-by: Bart Van Assche <bart.vanassche@...disk.com>---end quoted text---
Powered by blists - more mailing lists