From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from verein.lst.de ([213.95.11.211]:38392 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751124AbdENF6u (ORCPT ); Sun, 14 May 2017 01:58:50 -0400 Date: Sun, 14 May 2017 07:58:48 +0200 From: Christoph Hellwig To: davem@davemloft.net Cc: Bart Van Assche , "davem@davemloft.net" , "netdev@vger.kernel.org" , "linux-rdma@vger.kernel.org" , "stable@vger.kernel.org" , "ubraun@linux.vnet.ibm.com" Subject: Re: [PATCH] net/smc: mark as BROKEN due to remote memory exposure Message-ID: <20170514055848.GA23149@lst.de> References: <20170510072627.12060-1-hch@lst.de> <1494514662.2489.1.camel@sandisk.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1494514662.2489.1.camel@sandisk.com> Sender: stable-owner@vger.kernel.org List-ID: 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 ---end quoted text---