From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 1/3] IB/uverbs: reject invalid or unknown opcodes Date: Tue, 25 Aug 2015 10:55:08 +0200 Message-ID: <20150825085508.GC31630@lst.de> References: <1440002254-795-1-git-send-email-hch@lst.de> <20150822082516.GC1857@lst.de> <55DABF1E.2050804@mellanox.com> <20150824065501.GA31990@lst.de> <55DACED9.4060603@mellanox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <55DACED9.4060603@mellanox.com> Sender: stable-owner@vger.kernel.org To: Haggai Eran Cc: Christoph Hellwig , Sagi Grimberg , Doug Ledford , Sean Hefty , Hal Rosenstock , Eli Cohen , "linux-rdma@vger.kernel.org" , "stable@vger.kernel.org" List-Id: linux-rdma@vger.kernel.org On Mon, Aug 24, 2015 at 10:59:21AM +0300, Haggai Eran wrote: > > It looks odd to me as well, but it's not really something I want to > > change in this series. Note that sparse annoted types like __be32 > > aren't really common in userspace, but with a bit of effort they can > > be supported. We have them and regularly run sparse for xfsprogs for > > example. > > I have to try it with libibverbs sometime. It doesn't use uapi yet > though IIRC - it has its own version of the header files. Yes, I noticed that. And the WR opcodes aren't even exported in the uapi header, and use a shared namespace with the in-kernel only ones. It's all a giant mess unfortunately.