Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp29031ybz; Tue, 21 Apr 2020 04:06:47 -0700 (PDT) X-Google-Smtp-Source: APiQypKvhOWmSVfQND6XRuHbZ/7qYGGdKHUVycataK+oXzerYvkY4NQCw4ev/V83ZA3CF1x7lhzN X-Received: by 2002:a05:6402:b03:: with SMTP id bm3mr17638943edb.299.1587467207527; Tue, 21 Apr 2020 04:06:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587467207; cv=none; d=google.com; s=arc-20160816; b=XQkPf0nY2ukYfVVKdUmZ/UFHggMXV0iniW1jfzy+RbT695efW3SOWhlLbTqW/Snb7W PFuYZY0BCfUqC4+i4IPCYik+2Kafo14mxzgRqgI2AL9VGXzrgIRL2PyTnGP7gDkfoujg wOz+YaQuJWTvLHbrL8HaEftA1T6ij+bDekJjtFOooyKKI2+46yO6qVeKxr5ldHQhfuWg CyZ4/mVybx7ha90ij7fo/WBZaP+EyUqeJdVL6jY5f2beA9FozXUHi4+WHqd4hOYvv69b de3KVxZHa0hauKS7P8S/T7VOUfPPI9iw4aogux44m4AvAYCOzwzYwHzF+7v5bgA0vaox LEVA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date:from :references:cc:to:subject; bh=Z7Qkin+Pc+5as5LCVV5rKLP4PP3yfo5Gvg73bds/oY4=; b=0WEDK+XZ9jUGc5Xkjgm9fL2nAMo8+PUNgjh2/XfyU+vDIHNUPx/jP35mJIERdI1Ifj If8WphxGC4Us9VfIQKREXapQVwhrQ5CEQhNG9BP7/GIGoByie23Dpe5os9D/bYzDJ239 gfX307oQWVHe3F/CU8Ft1wTU8yLUAdkMrjoWcju2DN/P6EkYI7pl9LHRxb2FcFeyp7bR YV7jLkQd9Z4R6/N9m2r+HEAQ9GpRkaocFX+EVekrlj4k/vtO5XJD3IAUNVy2+oI0BmhY 88O3uqAa1YvWrFHnzhDfhyhNlVzOADEQlOjscJ/fK7AVom68vj1TdwIFazSTwxkbY4xe yKOA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 30si1556073edr.255.2020.04.21.04.06.23; Tue, 21 Apr 2020 04:06:47 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728473AbgDULCr (ORCPT + 99 others); Tue, 21 Apr 2020 07:02:47 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:57038 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726018AbgDULCr (ORCPT ); Tue, 21 Apr 2020 07:02:47 -0400 Received: from pps.filterd (m0098421.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 03LB2iZS089165 for ; Tue, 21 Apr 2020 07:02:46 -0400 Received: from e06smtp04.uk.ibm.com (e06smtp04.uk.ibm.com [195.75.94.100]) by mx0a-001b2d01.pphosted.com with ESMTP id 30gg27mw4n-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 21 Apr 2020 07:02:44 -0400 Received: from localhost by e06smtp04.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 21 Apr 2020 12:01:50 +0100 Received: from b06cxnps3075.portsmouth.uk.ibm.com (9.149.109.195) by e06smtp04.uk.ibm.com (192.168.101.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Tue, 21 Apr 2020 12:01:47 +0100 Received: from b06wcsmtp001.portsmouth.uk.ibm.com (b06wcsmtp001.portsmouth.uk.ibm.com [9.149.105.160]) by b06cxnps3075.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 03LB2VZd61997204 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 21 Apr 2020 11:02:31 GMT Received: from b06wcsmtp001.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 9FD91A4067; Tue, 21 Apr 2020 11:02:31 +0000 (GMT) Received: from b06wcsmtp001.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 6DC44A4054; Tue, 21 Apr 2020 11:02:31 +0000 (GMT) Received: from pic2.home (unknown [9.145.42.232]) by b06wcsmtp001.portsmouth.uk.ibm.com (Postfix) with ESMTP; Tue, 21 Apr 2020 11:02:31 +0000 (GMT) Subject: Re: [PATCH AUTOSEL 5.4 69/78] powerpc/powernv/ioda: Fix ref count for devices with their own PE To: Sasha Levin , linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Andrew Donnellan , Michael Ellerman , linuxppc-dev@lists.ozlabs.org References: <20200418144047.9013-1-sashal@kernel.org> <20200418144047.9013-69-sashal@kernel.org> From: Frederic Barrat Date: Tue, 21 Apr 2020 13:02:31 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <20200418144047.9013-69-sashal@kernel.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TM-AS-GCONF: 00 x-cbid: 20042111-0016-0000-0000-000003088DB2 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 20042111-0017-0000-0000-0000336CA446 Message-Id: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138,18.0.676 definitions=2020-04-21_04:2020-04-20,2020-04-21 signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 mlxscore=0 malwarescore=0 suspectscore=0 spamscore=0 priorityscore=1501 clxscore=1031 adultscore=0 lowpriorityscore=0 bulkscore=0 mlxlogscore=999 impostorscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2004210084 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Le 18/04/2020 à 16:40, Sasha Levin a écrit : > From: Frederic Barrat > > [ Upstream commit 05dd7da76986937fb288b4213b1fa10dbe0d1b33 ] This shouldn't be backported to stable. Fred > The pci_dn structure used to store a pointer to the struct pci_dev, so > taking a reference on the device was required. However, the pci_dev > pointer was later removed from the pci_dn structure, but the reference > was kept for the npu device. > See commit 902bdc57451c ("powerpc/powernv/idoa: Remove unnecessary > pcidev from pci_dn"). > > We don't need to take a reference on the device when assigning the PE > as the struct pnv_ioda_pe is cleaned up at the same time as > the (physical) device is released. Doing so prevents the device from > being released, which is a problem for opencapi devices, since we want > to be able to remove them through PCI hotplug. > > Now the ugly part: nvlink npu devices are not meant to be > released. Because of the above, we've always leaked a reference and > simply removing it now is dangerous and would likely require more > work. There's currently no release device callback for nvlink devices > for example. So to be safe, this patch leaks a reference on the npu > device, but only for nvlink and not opencapi. > > Signed-off-by: Frederic Barrat > Reviewed-by: Andrew Donnellan > Signed-off-by: Michael Ellerman > Link: https://lore.kernel.org/r/20191121134918.7155-2-fbarrat@linux.ibm.com > Signed-off-by: Sasha Levin > --- > arch/powerpc/platforms/powernv/pci-ioda.c | 19 ++++++++++++------- > 1 file changed, 12 insertions(+), 7 deletions(-) > > diff --git a/arch/powerpc/platforms/powernv/pci-ioda.c b/arch/powerpc/platforms/powernv/pci-ioda.c > index 058223233088e..e9cda7e316a50 100644 > --- a/arch/powerpc/platforms/powernv/pci-ioda.c > +++ b/arch/powerpc/platforms/powernv/pci-ioda.c > @@ -1062,14 +1062,13 @@ static struct pnv_ioda_pe *pnv_ioda_setup_dev_PE(struct pci_dev *dev) > return NULL; > } > > - /* NOTE: We get only one ref to the pci_dev for the pdn, not for the > - * pointer in the PE data structure, both should be destroyed at the > - * same time. However, this needs to be looked at more closely again > - * once we actually start removing things (Hotplug, SR-IOV, ...) > + /* NOTE: We don't get a reference for the pointer in the PE > + * data structure, both the device and PE structures should be > + * destroyed at the same time. However, removing nvlink > + * devices will need some work. > * > * At some point we want to remove the PDN completely anyways > */ > - pci_dev_get(dev); > pdn->pe_number = pe->pe_number; > pe->flags = PNV_IODA_PE_DEV; > pe->pdev = dev; > @@ -1084,7 +1083,6 @@ static struct pnv_ioda_pe *pnv_ioda_setup_dev_PE(struct pci_dev *dev) > pnv_ioda_free_pe(pe); > pdn->pe_number = IODA_INVALID_PE; > pe->pdev = NULL; > - pci_dev_put(dev); > return NULL; > } > > @@ -1205,6 +1203,14 @@ static struct pnv_ioda_pe *pnv_ioda_setup_npu_PE(struct pci_dev *npu_pdev) > struct pci_controller *hose = pci_bus_to_host(npu_pdev->bus); > struct pnv_phb *phb = hose->private_data; > > + /* > + * Intentionally leak a reference on the npu device (for > + * nvlink only; this is not an opencapi path) to make sure it > + * never goes away, as it's been the case all along and some > + * work is needed otherwise. > + */ > + pci_dev_get(npu_pdev); > + > /* > * Due to a hardware errata PE#0 on the NPU is reserved for > * error handling. This means we only have three PEs remaining > @@ -1228,7 +1234,6 @@ static struct pnv_ioda_pe *pnv_ioda_setup_npu_PE(struct pci_dev *npu_pdev) > */ > dev_info(&npu_pdev->dev, > "Associating to existing PE %x\n", pe_num); > - pci_dev_get(npu_pdev); > npu_pdn = pci_get_pdn(npu_pdev); > rid = npu_pdev->bus->number << 8 | npu_pdn->devfn; > npu_pdn->pe_number = pe_num; >