[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170516163539.GA5491@lst.de>
Date: Tue, 16 May 2017 18:35:39 +0200
From: Christoph Hellwig <hch@....de>
To: David Miller <davem@...emloft.net>
Cc: hch@....de, dledford@...hat.com, Bart.VanAssche@...disk.com,
torvalds@...ux-foundation.org, netdev@...r.kernel.org,
linux-rdma@...r.kernel.org, stable@...r.kernel.org,
ubraun@...ux.vnet.ibm.com
Subject: Re: [PATCH] net/smc: mark as BROKEN due to remote memory exposure
On Tue, May 16, 2017 at 12:33:08PM -0400, David Miller wrote:
> That doesn't cover things that don't directly touch the RDMA code or
> infiniband infrastructure.
>
> There should have been RDMA people on netdev who saw this thing and
> cried wolf, and they would have had about an entire year, and about
> 8 instances of this series being posted in which to do so.
>
> It's not like this got posted once or twice and went in with zero
> review.
None outside of netdev. Really, if you get rdma patches include
linux-rdma. Or at least linux-kernel where I will usually catch
this sort of stuff. netdev is too high traffic and too far away
from my area of work to watch it.
But for example when I wrote my first RDMA ULP I did subsribe
to linux-rdma, started extensive discussions and fixed up lots
of core code. There is no excuse for other people to not even
try.
Powered by blists - more mailing lists