Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp2320196imm; Wed, 16 May 2018 11:02:16 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpsILhYyHe9b2KC/miqlMjGGIOEHFf4iPYoVawyvV5b9NHAZswOsdgxuE5pqRnTjYp/TrJL X-Received: by 2002:a63:6f8a:: with SMTP id k132-v6mr1483111pgc.200.1526493736299; Wed, 16 May 2018 11:02:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526493736; cv=none; d=google.com; s=arc-20160816; b=JBCndB9twYt7QB/RdEOnxj7dPd1xBnelBIa1ZM2LpQq6zZ9OPeiZJs+a/DN1uI8eGL 97gd/A1KQw89LzaDWMiOHsdCWlK1bbylnvnEtGzCs5Vira2t4/3q/wAXmd1/nHPPNNka otp6De4SOOGDL76ot/HhkbzIFpSORwVfMleU3Tx1QsG2TJrfFDyaCzZkN76y2412Mr6J VJrNtRcIktJt6WRStLASC0j60nqOoP6MbNLfaBQTSfM+kkBfJ1PSKxJILqO3Q03y1cDo 4tnhEyMegVbtwM50FbqpKl0x4GFaq/+c0Cvav1WELrQVh659mJ3ZeX9eHRGFoysQZ8Co Y9XQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :arc-authentication-results; bh=xjHCyFSCc/sVMjX4aM9lyxEQOpUVmOqRbV6IURaIUn8=; b=QvtGt8SU3jD6gXKQzxWxLj7FEMzwbTjbVjgc1/tacPQdi1VlO0nba2o3nDkjdOl+RT KO5BsbuaextC2pc8T/xlxYV8XghoG3Bl3YIMHqNPL11fNSZCYBJxfgpgLvI7XKcbIUGK YIWKcKYnp/8PxgScxXEMsBsig3T7pOkV9e15C2/wm/YIuo2EnqeHUVQMk9gXSuIF7MmN 1JKZ9qUCAWc3d0qPo7u2lr7nWhdvEqzVs+InbbGFsm/Dpk5UBJD6rNGDjp07fXlfujlH qWMTjZIFWYJ8AOz95QsyGqYgmYyu12Fj53UwLbBrBe8ZVe1Ksg1W4sO9Cy/mTCbdEpqq +oUQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ziepe.ca header.s=google header.b=MBX9xuTv; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p2-v6si2528584pgs.498.2018.05.16.11.02.01; Wed, 16 May 2018 11:02:16 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@ziepe.ca header.s=google header.b=MBX9xuTv; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751430AbeEPSBX (ORCPT + 99 others); Wed, 16 May 2018 14:01:23 -0400 Received: from mail-wr0-f174.google.com ([209.85.128.174]:33460 "EHLO mail-wr0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750759AbeEPSBV (ORCPT ); Wed, 16 May 2018 14:01:21 -0400 Received: by mail-wr0-f174.google.com with SMTP id o4-v6so2540791wrm.0 for ; Wed, 16 May 2018 11:01:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ziepe.ca; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=xjHCyFSCc/sVMjX4aM9lyxEQOpUVmOqRbV6IURaIUn8=; b=MBX9xuTvSDhrWaR5HdIFQfVvEOnbGkm1Vjx/w7M4Cu0ZKRSfZCJ35x8uiKdhbrSMX5 /YsDztmYd85xCFjEXZIBocY4iccmrup/Yb2xOJVBb4y5nU2m9l/sJPSAkGseiZQ/f9Ex 2qgtMKvPAoizxe99a5xsY71F/UVT3dJs+wCbSbPCMjAhMPS2nDW91LBaynNGIYFTukT/ yfvHOJVt/g+rtUEO59U519h/YiMXIkpFBWU34PDl058jyRLDvq0JTclaTlTq1O1HhQgb AMnkPr+TunqvqqCd/zNzgv8lGv+ixmvVWsgceXe/AWGO0MbWnEHMGeeAAUky2wYZAzmq eauw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=xjHCyFSCc/sVMjX4aM9lyxEQOpUVmOqRbV6IURaIUn8=; b=bY+jqT3L+S1QyM26Cvbluq6UN3X8g5QI/ELsZzvzBKHxjtvCcYxPgxa3iYc/wvUCHq 7raJiSVIH1FFEU5ehPiACDC4+tcbRnLZn20g5mhbEdHAen66slGAei8Uo4sYRqjT0Kkb 3MxIx/0brYzc/zeFvH8ayAZXuhEb7MtlNyHKn/4Hlv6cVkTcc3iE0+xKRVqIC2X6ofeY SrTCmIox6OdGz/uXPvIwX3HFzSRG+d2DgYfbCraFOYeOQnLngyqhPcMc8CkRgb7j0+HC jrP4tfJgDddBnpaxfXQLT3WLjmkB+xs1o+48DuUlwazZwjTXYxE16JhkfOKwVd6ejel/ II6w== X-Gm-Message-State: ALKqPwe/q2fUvTH9YKnWuxXDCv04KDR+PQ2iJ+aOm+4qYUIiymEq4iK0 +wzkbBadxUzmJn8cXlItvp8bAQ== X-Received: by 2002:adf:e8c2:: with SMTP id k2-v6mr1531864wrn.182.1526493680226; Wed, 16 May 2018 11:01:20 -0700 (PDT) Received: from ziepe.ca (S010614cc2056d97f.ed.shawcable.net. [174.3.196.123]) by smtp.gmail.com with ESMTPSA id v12-v6sm2892478wrm.68.2018.05.16.11.01.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 16 May 2018 11:01:19 -0700 (PDT) Received: from jgg by mlx.ziepe.ca with local (Exim 4.86_2) (envelope-from ) id 1fJ0jj-0007RF-CW; Wed, 16 May 2018 12:01:15 -0600 Date: Wed, 16 May 2018 12:01:15 -0600 From: Jason Gunthorpe To: =?utf-8?B?SMOla29u?= Bugge Cc: Doug Ledford , Don Hiatt , Ira Weiny , Sean Hefty , OFED mailing list , linux-kernel@vger.kernel.org, Hal Rosenstock Subject: Re: [PATCH IB/core 2/2] IB/cm: Send authentic pkey in REQ msg and check eligibility of the pkeys Message-ID: <20180516180115.GF25661@ziepe.ca> References: <3bee76df-49a6-cf3c-6df4-749a6309358e@dev.mellanox.co.il> <20180514210200.GN21531@ziepe.ca> <20180515190424.GL5615@ziepe.ca> <3E15B62F-E705-43BD-8A72-9E74F784D40E@oracle.com> <20180516151201.GA25661@ziepe.ca> <695ae613-931a-50ba-2b83-9d172e0ac2bc@dev.mellanox.co.il> <151B2A36-28F0-4A88-8633-31AE7E55F848@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <151B2A36-28F0-4A88-8633-31AE7E55F848@oracle.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 16, 2018 at 07:46:10PM +0200, HÃ¥kon Bugge wrote: > OK. Lets take one example. The pkey table contains 0xFFFF, 0x8001, > 0x0001. > > The wce.pkey_index is 1 (i.e., pointing to 0x8001). Now, tell me, was > BTH.PKey 0x8001 (matches 0x8001) or was it 0x0001 (also matching > 0x8001) ? As far as the Linux core is concerned, it must have been 0x8001, because the only way the pkey_index feature works properly is if exact-match takes precedence over in-exact match. Jason