Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp996998yba; Thu, 4 Apr 2019 02:03:24 -0700 (PDT) X-Google-Smtp-Source: APXvYqzioEzHzNYYrqDVeQS9lrdYTakSGA0RQxSeTWFPkx5FNxM9CfykdoFf4+pjO5fsXTuSQBQo X-Received: by 2002:a62:6444:: with SMTP id y65mr4664633pfb.56.1554368604444; Thu, 04 Apr 2019 02:03:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554368604; cv=none; d=google.com; s=arc-20160816; b=UfltxRAmzobA/2YJuuDKQwJwz+hQIeVabwk1nEOYgIRIzmKmWdHOkjBTiKHUY7drW4 BnlHZKE7Cvuv+fWDyC3sW0dKGcJ06lGndi/ydU+j9aXVUaF/30b6BRfQmgF6ZFOivvlB oFBjllvOnvrTJsL3Q3STzJRQdyeHR3Z32havX77rrmyl2BCbLcZzhm2URyGZBoTxMpwA MmvT5dbKmcvQEmZ+15x+lg5NxkhrOZTN+g+Oyb2txuM+ZLkk4tLAwh0RBfGuQBcjIbZD hPrlYgCxe9bLAsICJZ/bKE2pTm6N5SPSM71dLjyQVa8dUkvyAGSLnxXFvQWVUoiR+TMZ krtQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=W7Aj5OK6fg91U8a7y3uELJsMAJuA62R4pii8TZfpnOU=; b=xihq++KrWggptNHUgDNzSpMu3TV8CwsjxNYXqigM0Uh6aR6QI1a5Tw6+g+CNWaa4qy FlQZs4Ch/Ajd7ff74wUCcn9LhUKN5WKn0nr1a6cYUt0cA/4lfq7Chiq6ttgFPy+ZTK/w NRMIZyO4ZSLlQf8T82d5E1He6luUbP7C3t88asx+RuPMk+nJYXJxJy48W1nywdTgeB2G VhngA94dZsnTumtC5MSZsa4R1sOcjC+VzilfOic2cY2G+Dxu3OXxI8VFcQ2LGyc/Y6B4 WBYAuE4pRcz3n1Im32I2zyk9ZwIgx49a5amRrJkUie3IjE86kmXIr3KO7AKrJIG9obV/ lHSw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=a2hundlP; 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 g96si16666944plb.168.2019.04.04.02.03.08; Thu, 04 Apr 2019 02:03:24 -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=@kernel.org header.s=default header.b=a2hundlP; 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 S1731393AbfDDJCa (ORCPT + 99 others); Thu, 4 Apr 2019 05:02:30 -0400 Received: from mail.kernel.org ([198.145.29.99]:39812 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731165AbfDDJC1 (ORCPT ); Thu, 4 Apr 2019 05:02:27 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 632932183E; Thu, 4 Apr 2019 09:02:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1554368545; bh=MaOrEPJYF96PL0l6fbD/UNDw6yjuGMJWPbXIS2h0lPA=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=a2hundlPgPdBVp6b7iOiJmFNyCCcm2qxSM9FEX+y5cFLD5AeGZNw/RPceHiXyoEL6 dLHXdlUbUgNYg8e2vLrxd4nGFaMyRauxkSiD1iCiwRPgoxk333fdfkYvgSEsxu0Ynv Dkcftbi3ytXfgD3skNb1i02jolGYYj76oHGsQBmk= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Alexey Kardashevskiy , David Gibson , Michael Ellerman , Sasha Levin Subject: [PATCH 4.19 053/187] powerpc/powernv/ioda: Fix locked_vm counting for memory used by IOMMU tables Date: Thu, 4 Apr 2019 10:46:30 +0200 Message-Id: <20190404084605.589545542@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190404084603.119654039@linuxfoundation.org> References: <20190404084603.119654039@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review X-Patchwork-Hint: ignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.19-stable review patch. If anyone has any objections, please let me know. ------------------ [ Upstream commit 11f5acce2fa43b015a8120fa7620fa4efd0a2952 ] We store 2 multilevel tables in iommu_table - one for the hardware and one with the corresponding userspace addresses. Before allocating the tables, the iommu_table_group_ops::get_table_size() hook returns the combined size of the two and VFIO SPAPR TCE IOMMU driver adjusts the locked_vm counter correctly. When the table is actually allocated, the amount of allocated memory is stored in iommu_table::it_allocated_size and used to decrement the locked_vm counter when we release the memory used by the table; .get_table_size() and .create_table() calculate it independently but the result is expected to be the same. However the allocator does not add the userspace table size to .it_allocated_size so when we destroy the table because of VFIO PCI unplug (i.e. VFIO container is gone but the userspace keeps running), we decrement locked_vm by just a half of size of memory we are releasing. To make things worse, since we enabled on-demand allocation of indirect levels, it_allocated_size contains only the amount of memory actually allocated at the table creation time which can just be a fraction. It is not a problem with incrementing locked_vm (as get_table_size() value is used) but it is with decrementing. As the result, we leak locked_vm and may not be able to allocate more IOMMU tables after few iterations of hotplug/unplug. This sets it_allocated_size in the pnv_pci_ioda2_ops::create_table() hook to what pnv_pci_ioda2_get_table_size() returns so from now on we have a single place which calculates the maximum memory a table can occupy. The original meaning of it_allocated_size is somewhat lost now though. We do not ditch it_allocated_size whatsoever here and we do not call get_table_size() from vfio_iommu_spapr_tce.c when decrementing locked_vm as we may have multiple IOMMU groups per container and even though they all are supposed to have the same get_table_size() implementation, there is a small chance for failure or confusion. Fixes: 090bad39b237 ("powerpc/powernv: Add indirect levels to it_userspace") Signed-off-by: Alexey Kardashevskiy Reviewed-by: David Gibson Signed-off-by: Michael Ellerman Signed-off-by: Sasha Levin --- arch/powerpc/platforms/powernv/pci-ioda-tce.c | 1 - arch/powerpc/platforms/powernv/pci-ioda.c | 7 ++++++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/arch/powerpc/platforms/powernv/pci-ioda-tce.c b/arch/powerpc/platforms/powernv/pci-ioda-tce.c index 7639b2168755..f5adb6b756f7 100644 --- a/arch/powerpc/platforms/powernv/pci-ioda-tce.c +++ b/arch/powerpc/platforms/powernv/pci-ioda-tce.c @@ -313,7 +313,6 @@ long pnv_pci_ioda2_table_alloc_pages(int nid, __u64 bus_offset, page_shift); tbl->it_level_size = 1ULL << (level_shift - 3); tbl->it_indirect_levels = levels - 1; - tbl->it_allocated_size = total_allocated; tbl->it_userspace = uas; tbl->it_nid = nid; diff --git a/arch/powerpc/platforms/powernv/pci-ioda.c b/arch/powerpc/platforms/powernv/pci-ioda.c index cde710297a4e..326ca6288bb1 100644 --- a/arch/powerpc/platforms/powernv/pci-ioda.c +++ b/arch/powerpc/platforms/powernv/pci-ioda.c @@ -2603,8 +2603,13 @@ static long pnv_pci_ioda2_create_table_userspace( int num, __u32 page_shift, __u64 window_size, __u32 levels, struct iommu_table **ptbl) { - return pnv_pci_ioda2_create_table(table_group, + long ret = pnv_pci_ioda2_create_table(table_group, num, page_shift, window_size, levels, true, ptbl); + + if (!ret) + (*ptbl)->it_allocated_size = pnv_pci_ioda2_get_table_size( + page_shift, window_size, levels); + return ret; } static void pnv_ioda2_take_ownership(struct iommu_table_group *table_group) -- 2.19.1