From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B1D2AC742CA for ; Fri, 12 Jul 2019 15:24:34 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 93279208E4 for ; Fri, 12 Jul 2019 15:24:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727161AbfGLPYe (ORCPT ); Fri, 12 Jul 2019 11:24:34 -0400 Received: from stargate.chelsio.com ([12.32.117.8]:43766 "EHLO stargate.chelsio.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727079AbfGLPYd (ORCPT ); Fri, 12 Jul 2019 11:24:33 -0400 Received: from localhost (mehrangarh.blr.asicdesigners.com [10.193.185.169]) by stargate.chelsio.com (8.13.8/8.13.8) with ESMTP id x6CFOKMm029692; Fri, 12 Jul 2019 08:24:26 -0700 Date: Fri, 12 Jul 2019 20:54:20 +0530 From: Potnuri Bharat Teja To: Jason Gunthorpe Cc: "linux-rdma@vger.kernel.org" , "BMT@zurich.ibm.com" , "monis@mellanox.com" , Nirranjan Kirubaharan Subject: Re: User SIW fails matching device Message-ID: <20190712152418.GA16331@chelsio.com> References: <20190712142718.GA26697@chelsio.com> <20190712143546.GD27512@ziepe.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190712143546.GD27512@ziepe.ca> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-rdma-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-rdma@vger.kernel.org On Friday, July 07/12/19, 2019 at 20:05:46 +0530, Jason Gunthorpe wrote: > On Fri, Jul 12, 2019 at 07:57:19PM +0530, Potnuri Bharat Teja wrote: > > Hi all, > > I observe the following behavior on one of my machines configured for siw. > > > > Issue: > > SIW device gets wrong device ops (HW/real rdma driver device ops) instead of > > siw device ops due to improper device matching. > > > > Root-cause: > > In libibverbs, during user cma initialisation, for each entry from the driver > > list, sysfs device is checked for matching name or device. > > If the siw/rxe driver is at the head of the list, then sysfs device matches > > properly with the corresponding siw driver and gets the corresponding siw/rxe > > device ops. Now, If the siw/rxe driver is after the real HW driver cxgb4/mlx5 > > respectively in the driver list, then siw sysfs device matches pci device and > > wrongly gets the device ops of HW driver (cxgb4/mlx5). > > > > Below debug prints from verbs_register_driver() and driver_list entries, where > > siw is after cxgb4. I see verbs alloc context landing in cxgb4_alloc_context > > instead of siw_alloc_context, thus breaking user siw. > > > > verbs_register_driver_22: 184: driver 0x176e370 > > verbs_register_driver_22: 185: name ipathverbs > > verbs_register_driver_22: 184: driver 0x176f6a0 > > verbs_register_driver_22: 185: name cxgb4 > > verbs_register_driver_22: 184: driver 0x176fd50 > > verbs_register_driver_22: 185: name cxgb3 > > verbs_register_driver_22: 184: driver 0x1777020 > > verbs_register_driver_22: 185: name rxe > > verbs_register_driver_22: 184: driver 0x1770a30 > > verbs_register_driver_22: 185: name siw > > verbs_register_driver_22: 184: driver 0x1771120 > > verbs_register_driver_22: 185: name mlx4 > > verbs_register_driver_22: 184: driver 0x1771990 > > verbs_register_driver_22: 185: name mlx5 > > verbs_register_driver_22: 184: driver 0x1771ff0 > > verbs_register_driver_22: 185: name efa > > > > try_drivers: 372: driver 0x176e370, sysfs_dev 0x1776b20, name: ipathverbs > > try_drivers: 372: driver 0x176f6a0, sysfs_dev 0x1776b20, name: cxgb4 > > try_drivers: 372: driver 0x176fd50, sysfs_dev 0x1776b20, name: cxgb3 > > try_drivers: 372: driver 0x1777020, sysfs_dev 0x1776b20, name: rxe > > try_drivers: 372: driver 0x1770a30, sysfs_dev 0x1776b20, name: siw > > try_drivers: 372: driver 0x1771120, sysfs_dev 0x1776b20, name: mlx4 > > try_drivers: 372: driver 0x1771990, sysfs_dev 0x1776b20, name: mlx5 > > try_drivers: 372: driver 0x1771ff0, sysfs_dev 0x1776b20, name: efa > > > > Proposed fix: > > I have the below fix that works. It adds siw/rxe driver to the HEAD of the > > driver list and the rest to the tail. I am not sure if this fix is the ideal > > one, so I am attaching it to this mail. > > Update your rdma-core to latest and this will be fixed fully by using > netlink to match the siw device.. > I pulled the latest rdma-core, still see the issue. commit 7ef6077ec3201f661458297fea776746ba752843 (HEAD, upstream/master) Merge: 837954ff677c 95934b61a74e Author: Jason Gunthorpe Date: Thu Jul 11 16:18:06 2019 -0300 Merge pull request #539 from jgunthorpe/netlink Use netlink to learn about ibdevs and their related chardevs ----------- Is there any corresponding kernel change or package dependency? I am currently on Doug's wip/dl-for-next branch.