Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp2231586imm; Thu, 7 Jun 2018 07:26:06 -0700 (PDT) X-Google-Smtp-Source: ADUXVKLNwYZVyNN+gWBT3ZDLNVDKRkCeY+nIekZ9AcchO3G6+N+4qhFNVVPsGtAmhmvk9OkLjx7a X-Received: by 2002:a62:e310:: with SMTP id g16-v6mr2004796pfh.25.1528381566670; Thu, 07 Jun 2018 07:26:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528381566; cv=none; d=google.com; s=arc-20160816; b=cuK0v7LGas7g4hVfcqUf7gRpNl7ub9y3ZVtrgLE+PW2RJFj6WYij8z2pZZkFBZlddJ 87CKe4PA/dyGGqnWEur75qMV8Bd6aJeO2703TA8TLPRZqYdlc4IPLVJPkR5naVaJM2cR Z4kT9cvJ/oty6FftEMH41hALBRyb3Q6p7Fa4HkYcLOLsyV0ujKlsetnkkuYZk0f1WL22 1zg7pZST6Zsa1DMMnKk/MNdx8TKOWPx1tMDuh3/fgHBhx7oDvdXiYCRbZMYO3jlCN4LQ IfmRQ1VEyfc4LDBXGeMpmgLMlg2fT9xHnHsUWEf2ZqaNWdpRId+ncSb6wSIAzgBO5kYH i2CA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:subject:message-id:date:cc:to :from:mime-version:content-transfer-encoding:content-disposition :arc-authentication-results; bh=PS01tSC2oYy5LDy8g8QAwwRQ0oNZQlG9qj0W/5Q/Gy0=; b=IWNDRmVrRaapYM/RCO/TC+MMNSFXzPPIJtUAJX4QHEfUvCnxcX0f3UKWaDyNPVJukI 7F4kBXqae3/u+lZUXhOjmaePHtiqSU6FfJ5/iDoy1Q1LJEEa38FrbjSDuXZrO1dVEEJf YkuZYryF33ZCaepRO3MkfID6uScbgDBvz07T8WJOEdvy+f/Gkw0fzej0GA2peRuhmwQ2 FyLJlo8CksF4xqgaokEoSuJapFpGxUYYCRUe7vwn9ZnkXndfWKRyXmOgq8PhzZW4r3w5 K80QUd7vjGrgoppoWwSLIT6oXsupFAEmAbZJVer6sJ6RHZXnP5gzpDX4+RQEwVacQFxg H4og== ARC-Authentication-Results: i=1; mx.google.com; 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 f8-v6si28646364pgr.35.2018.06.07.07.25.52; Thu, 07 Jun 2018 07:26:06 -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; 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 S933500AbeFGOYi (ORCPT + 99 others); Thu, 7 Jun 2018 10:24:38 -0400 Received: from shadbolt.e.decadent.org.uk ([88.96.1.126]:40129 "EHLO shadbolt.e.decadent.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933335AbeFGOYe (ORCPT ); Thu, 7 Jun 2018 10:24:34 -0400 Received: from [148.252.241.226] (helo=deadeye) by shadbolt.decadent.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1fQvbp-0005Zj-7b; Thu, 07 Jun 2018 15:09:49 +0100 Received: from ben by deadeye with local (Exim 4.91) (envelope-from ) id 1fQvb2-0002rw-Ka; Thu, 07 Jun 2018 15:09:00 +0100 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 From: Ben Hutchings To: linux-kernel@vger.kernel.org, stable@vger.kernel.org CC: akpm@linux-foundation.org, "Leon Romanovsky" , "Jack Morgenstein" , "Jason Gunthorpe" Date: Thu, 07 Jun 2018 15:05:21 +0100 Message-ID: X-Mailer: LinuxStableQueue (scripts by bwh) Subject: [PATCH 3.16 132/410] IB/mlx4: Fix incorrectly releasing steerable UD QPs when have only ETH ports In-Reply-To: X-SA-Exim-Connect-IP: 148.252.241.226 X-SA-Exim-Mail-From: ben@decadent.org.uk X-SA-Exim-Scanned: No (on shadbolt.decadent.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 3.16.57-rc1 review patch. If anyone has any objections, please let me know. ------------------ From: Jack Morgenstein commit 852f6927594d0d3e8632c889b2ab38cbc46476ad upstream. Allocating steerable UD QPs depends on having at least one IB port, while releasing those QPs does not. As a result, when there are only ETH ports, the IB (RoCE) driver requests releasing a qp range whose base qp is zero, with qp count zero. When SR-IOV is enabled, and the VF driver is running on a VM over a hypervisor which treats such qp release calls as errors (rather than NOPs), we see lines in the VM message log like: mlx4_core 0002:00:02.0: Failed to release qp range base:0 cnt:0 Fix this by adding a check for a zero count in mlx4_release_qp_range() (which thus treats releasing 0 qps as a nop), and eliminating the check for device managed flow steering when releasing steerable UD QPs. (Freeing ib_uc_qpns_bitmap unconditionally is also OK, since it remains NULL when steerable UD QPs are not allocated). Fixes: 4196670be786 ("IB/mlx4: Don't allocate range of steerable UD QPs for Ethernet-only device") Signed-off-by: Jack Morgenstein Signed-off-by: Leon Romanovsky Signed-off-by: Jason Gunthorpe Signed-off-by: Ben Hutchings --- drivers/infiniband/hw/mlx4/main.c | 13 +++++-------- drivers/net/ethernet/mellanox/mlx4/qp.c | 3 +++ 2 files changed, 8 insertions(+), 8 deletions(-) --- a/drivers/infiniband/hw/mlx4/main.c +++ b/drivers/infiniband/hw/mlx4/main.c @@ -2272,9 +2272,8 @@ err_steer_free_bitmap: kfree(ibdev->ib_uc_qpns_bitmap); err_steer_qp_release: - if (ibdev->steering_support == MLX4_STEERING_MODE_DEVICE_MANAGED) - mlx4_qp_release_range(dev, ibdev->steer_qpn_base, - ibdev->steer_qpn_count); + mlx4_qp_release_range(dev, ibdev->steer_qpn_base, + ibdev->steer_qpn_count); err_counter: for (; i; --i) if (ibdev->counters[i - 1] != -1) @@ -2373,11 +2372,9 @@ static void mlx4_ib_remove(struct mlx4_d ibdev->iboe.nb.notifier_call = NULL; } - if (ibdev->steering_support == MLX4_STEERING_MODE_DEVICE_MANAGED) { - mlx4_qp_release_range(dev, ibdev->steer_qpn_base, - ibdev->steer_qpn_count); - kfree(ibdev->ib_uc_qpns_bitmap); - } + mlx4_qp_release_range(dev, ibdev->steer_qpn_base, + ibdev->steer_qpn_count); + kfree(ibdev->ib_uc_qpns_bitmap); if (ibdev->iboe.nb_inet.notifier_call) { if (unregister_inetaddr_notifier(&ibdev->iboe.nb_inet)) --- a/drivers/net/ethernet/mellanox/mlx4/qp.c +++ b/drivers/net/ethernet/mellanox/mlx4/qp.c @@ -257,6 +257,9 @@ void mlx4_qp_release_range(struct mlx4_d u64 in_param = 0; int err; + if (!cnt) + return; + if (mlx4_is_mfunc(dev)) { set_param_l(&in_param, base_qpn); set_param_h(&in_param, cnt);