Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp4836527imm; Mon, 14 May 2018 14:05:59 -0700 (PDT) X-Google-Smtp-Source: AB8JxZrIen7x9OKvsz9SxAMVPQknlxFoJfuk41WV72R9dclpZo+p3ND28JrEdGv0kNryJPkLgeg4 X-Received: by 2002:a62:98cb:: with SMTP id d72-v6mr11932658pfk.98.1526331959557; Mon, 14 May 2018 14:05:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526331959; cv=none; d=google.com; s=arc-20160816; b=bHyytfBicjSvwZywbQYL0SWpnzMImammlO12PVbdD1N78jC2fyLGzynaD0w1IvMDkz pk2oO+VHS8wSStp5HfOdx07BPudPvKovHi11pWvEPH8a/jxUik/2d825Yzn0zuOJCCOH WP6NFsEYsKdewEAeg0CyrP1q2Mj5LpvjGFc93pSbQMnLrfHUt9v6bzJsuL31GRRLAC27 gscHLtF7cGSjd6fY+v/jLuLhsSZtGE08I+eajQFJm94oPxFahIzRpAgBWIH/V77uWlXU fePTcFWTCLfiFGGdOYHRuiytAdnLVVL45pPmlDYWAl0GbsL5yCC+7kjvVJs5IbRJRdr3 E7BA== 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=X+s5oCacgXuwSxhWN+8SZlKmQ7KssJlwNcKV/xzqSwk=; b=Jm3zeSqfWhbt0G0KbrPhiOpAtDBIhwnD57eqFWNMj4LrniflsdkQnyI9aYhedfvRKX exWMNJ4BGl5xQg7K2miqeSYPWCwRCGNHNaIdBfA6xLZ9dhvNB8W2Ny2t9ujjN8Xna4FH 0bWeZ0R7Obp3FqcQZtz9xyJPs1RGmpL1mftlH/Ybb1R8Umh413WBPIE0ULBaDTaj7XCb jMfRxLDYwY0FuAop9Bblf+iEQNptWHgrtNhdX2snDCTFgPb9tvGin+nuRqowscWy7G1/ PmbfoIIt++22+JH/3ORQgoNuZujLrBKtjBNcxBXOpaKmJqBgzeWR3Qg6A1/F+SyhW4AY XPfQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ziepe.ca header.s=google header.b=GyrZB+TS; 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 f19-v6si10240159plj.89.2018.05.14.14.05.45; Mon, 14 May 2018 14:05:59 -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=GyrZB+TS; 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 S1752410AbeENVFI (ORCPT + 99 others); Mon, 14 May 2018 17:05:08 -0400 Received: from mail-wm0-f68.google.com ([74.125.82.68]:34770 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752650AbeENVEO (ORCPT ); Mon, 14 May 2018 17:04:14 -0400 Received: by mail-wm0-f68.google.com with SMTP id a137-v6so13295244wme.1 for ; Mon, 14 May 2018 14:04:13 -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=X+s5oCacgXuwSxhWN+8SZlKmQ7KssJlwNcKV/xzqSwk=; b=GyrZB+TSBdlKbjl+ehuuNDUtSgifkJfdyU0RVlztWPhosF6766M8Gbdg4tL+YOrQl/ mMWyGePVx7Ez9ZchLTAekFSQCQ1m/QTDtkSBJaYlU61hlQBz5GVU/lgGJD1aN5pSqYJ7 2z/C7qTrmvn47LRXfZLc/xw2onUfKjQ8rMzL6UoZJ7Y83RZv0g76yARKk04CjC/wF4bW 5CgX4qM/stMmW4ONRk7LuUvDpQR7p+704fJyG/Wa4tJc9SJ8VOMWFCOWdxu19VUm2HRq 8PHQS5Z7xsjgSXw/SM8qFQi60vQb0bb4G0ccUgbOYM/0DxXH1haNYM/5fdA1iMQXMqKG fMAA== 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=X+s5oCacgXuwSxhWN+8SZlKmQ7KssJlwNcKV/xzqSwk=; b=AWxLjZnaoFrYDfcq3mqAgflBm5Q3UC+A6TjwhKa4v2UAaYqHTNB+ubnxaAd/XxpIrG /JD+ZtX0smjshjozxO4XuW+KPo6ejNz3KcA2733ad1D0bhwSRRjffpN8lG5srmisCPUn LqxT3xUoN1qgjqXehYpbS8bD7wSEasD6wQuE623e0M2XTtR7KJmPXoNAEYzI08s6DeDF o0IMBqi76A7Jh73rfggt7C8f859kN73oH6btuhsJbB3yX3ClJqbaiNHF6CnmLzC0zmev r/AZHz/05NEWfV+3uJ0MQs/gfmM1mArI+9Hgvspt1yGRPM5sBv9E9f1SmFpxKcmsQLLn 1pIw== X-Gm-Message-State: ALKqPwddM/lMX0eb6y0iHgCpatsmG84Y82IEs8H4kci/AdtkLlbk+2m4 5b6Btp6S6rAE2/tkwn7xnqgasA== X-Received: by 2002:a1c:c013:: with SMTP id q19-v6mr6062688wmf.49.1526331853117; Mon, 14 May 2018 14:04:13 -0700 (PDT) Received: from ziepe.ca (S010614cc2056d97f.ed.shawcable.net. [174.3.196.123]) by smtp.gmail.com with ESMTPSA id l37-v6sm14938321wrl.83.2018.05.14.14.04.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 May 2018 14:04:12 -0700 (PDT) Received: from jgg by mlx.ziepe.ca with local (Exim 4.86_2) (envelope-from ) id 1fIKdc-0007Ke-IS; Mon, 14 May 2018 15:04:08 -0600 Date: Mon, 14 May 2018 15:04:08 -0600 From: Jason Gunthorpe To: =?utf-8?B?SMOla29u?= Bugge Cc: Hal Rosenstock , Doug Ledford , Don Hiatt , Ira Weiny , Sean Hefty , OFED mailing list , linux-kernel@vger.kernel.org Subject: Re: [PATCH IB/core 2/2] IB/cm: Send authentic pkey in REQ msg and check eligibility of the pkeys Message-ID: <20180514210408.GO21531@ziepe.ca> References: <20180509093020.24503-1-Haakon.Bugge@oracle.com> <20180509093020.24503-3-Haakon.Bugge@oracle.com> <3bee76df-49a6-cf3c-6df4-749a6309358e@dev.mellanox.co.il> <325ba4af-b52e-4f70-9d89-38dafe10ba99@dev.mellanox.co.il> <23B160D2-6631-42A6-8A4D-644E90E8A704@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <23B160D2-6631-42A6-8A4D-644E90E8A704@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 Fri, May 11, 2018 at 12:55:00PM +0200, Håkon Bugge wrote: > > I'll check upstream OpenSM when I get a chance to see if same problem > > exists. Oracle OpenSM forked from upstream long time ago and not sure > > how similar the path record code is. There were various impacts for the > > shared port virtualization (for CX-3) in terms of adding the ability to > > allow both pkeys. > > I just had a chat with Line H. here in Oracle. She confirms that Oracle’s SM and the upstream one act similar in this matter. > > Further, using shared port virtualization, OpenSM will adhere to the > physical ports only, and doesn’t even know the PKey assignments to > the VFs assigned the VMs. Yes, but that isn't the point. If the VM receives a PR with a pkey that is not found in the VM's table then it should not even send a CM REQ in the first place. Jason