Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1981560pxb; Mon, 18 Jan 2021 05:20:49 -0800 (PST) X-Google-Smtp-Source: ABdhPJy90YwVCSa3RCoC0bZCCMMJLgjHeLlcl9bpCaLd7VbnO8ilZKLOGgqT0pOpFLDTuO+K4UYw X-Received: by 2002:a17:906:f85:: with SMTP id q5mr17393479ejj.105.1610976049433; Mon, 18 Jan 2021 05:20:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610976049; cv=none; d=google.com; s=arc-20160816; b=aerKvP73TJtQsyjwx7z1gQqX84o7rWrKVHXdV5gEeplJfXRg/CoxMkE/ThfqbjlFS/ tjh7YqkhxRPH+d1/9Nj8p7GYlxgZ0p9MObeXaQdBH/wiLU7DbDOnXblQoOX5mfbBJ4ZD +RbHnB457gSTxoF/iPMB/Px2v+q754BqdMeJfLFlRxKp4l5UaqbjFaNeKTG62H9vn7mL nwUgrck/i5fYqNlNIbUyfwt3Em6IoprOjLa+36pHdptid2UZ/ed+1/0HtMaYrz4WpJWX fUVtK6f2ritz9vZaG2Tvm5Co1Dym3mKMj4LNc6XPIxEjgrJdvHchR3puXGXo9FNLeiEr gf3A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:dkim-signature:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=l3l11JUxFpok5jfXeALrLtW4EEP/3cDQ3PHNG0KaDhY=; b=B0aUj7bnY8zJl5bOn28OzgeVMRJFzYbDJCVS+Q2/j2uNde53QEQ4XbKJZdPs+JhLDU j33rdqhtRFZ7T1G4OIZfBPsNndWvcx/ApT5D0W2LEfhAAYquXwzxWf0mKNZZSjBEQoCl Bz+OMoDqW+pkyMLltuuPseBvLNIqVLYNtK+do3f+wHbargkkf3je1YLi9HQUa20FaPyq iu++qooOZos+eYQbvEM5c7v+5szXpdeqAFHTNXLxZblunLcD9P/yP3/cJe3mKOEBWvAF SuqOUXzBQe6xx5vNXFCEJ8xqNKKbtlMoUTUDnvITi43D+Ek5kL7T36ECKwabgIbc7kSH w+VA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=jRrqMxhJ; 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=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dk5si2125571edb.586.2021.01.18.05.20.26; Mon, 18 Jan 2021 05:20:49 -0800 (PST) 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; dkim=pass header.i=@nvidia.com header.s=n1 header.b=jRrqMxhJ; 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=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2404280AbhARNR0 (ORCPT + 99 others); Mon, 18 Jan 2021 08:17:26 -0500 Received: from hqnvemgate26.nvidia.com ([216.228.121.65]:13953 "EHLO hqnvemgate26.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2391494AbhARNRO (ORCPT ); Mon, 18 Jan 2021 08:17:14 -0500 Received: from hqmail.nvidia.com (Not Verified[216.228.121.13]) by hqnvemgate26.nvidia.com (using TLS: TLSv1.2, AES256-SHA) id ; Mon, 18 Jan 2021 05:16:18 -0800 Received: from mtl-vdi-166.wap.labs.mlnx (172.20.145.6) by HQMAIL107.nvidia.com (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 18 Jan 2021 13:16:11 +0000 Date: Mon, 18 Jan 2021 15:16:08 +0200 From: Eli Cohen To: Thomas Zimmermann CC: Christian =?iso-8859-1?Q?K=F6nig?= , , , , dri-devel , Subject: Re: Change eats memory on my server Message-ID: <20210118131608.GA50817@mtl-vdi-166.wap.labs.mlnx> References: <20210114151529.GA79120@mtl-vdi-166.wap.labs.mlnx> <23cf7712-1daf-23b8-b596-792c9586d6b4@suse.de> <20210117050837.GA225992@mtl-vdi-166.wap.labs.mlnx> <83f74a11-b3c0-db2e-8301-4292d60d803b@amd.com> <2ea2630b-8782-c662-91fe-683d8b5d6c99@suse.de> <20210118091302.GB40909@mtl-vdi-166.wap.labs.mlnx> <052812fd-10ce-abf4-d12a-91d4fd66ed54@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <052812fd-10ce-abf4-d12a-91d4fd66ed54@suse.de> User-Agent: Mutt/1.9.5 (bf161cf53efb) (2018-04-13) X-Originating-IP: [172.20.145.6] X-ClientProxiedBy: HQMAIL105.nvidia.com (172.20.187.12) To HQMAIL107.nvidia.com (172.20.187.13) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1610975778; bh=l3l11JUxFpok5jfXeALrLtW4EEP/3cDQ3PHNG0KaDhY=; h=Date:From:To:CC:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To:User-Agent: X-Originating-IP:X-ClientProxiedBy; b=jRrqMxhJ7q0y5UDTfh7isRbwgK1CaJpORosmdB/dQkPQaFgD/oUEY8jPFgDEeOVtT wdtvCaCdzFpjaKCfn+Gt+klO/xSrRBnSTiLYHQCJzJBh3K/SbVIl1etE9NSSt5grcJ iTDOGy0vmqj3aWfXVch/KFSnIK+l2b2amsODD/rHGTWrn8WciTIkmRUHps/eSZlT8I mj2L3J698a1juj4nwXSBg0+OUyhtQgXD0F0KU7lHfa/iRpMjYF/31gGQE45UUWMXFX kII/By6CXb5GkleFF4+sI+8p3CV26v39Uo7jp5UlHKgbTPR2Is7Fe4Or6givSx1Ax/ T2wMkU8G23cog== Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 18, 2021 at 10:30:56AM +0100, Thomas Zimmermann wrote: > > Here's the patch against the latest DRM tree. v5.11-rc3 should work as well. > > I was able to reproduce the memory leak locally and found that the patch > fixes it. Please give it a try. > As far as I am concerned, this issue is fixed by the patch you sent. Thanks for looking into it. Eli