Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp2334651pxb; Mon, 18 Jan 2021 15:14:51 -0800 (PST) X-Google-Smtp-Source: ABdhPJyniQ9XQZh+hLTsHby/UTS7d5+kJ2+fKLXjdqVBYJgn5lnJWjUggcP+Ox9avAF8fzSyhsmG X-Received: by 2002:a17:906:a2da:: with SMTP id by26mr1208598ejb.531.1611011690886; Mon, 18 Jan 2021 15:14:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611011690; cv=none; d=google.com; s=arc-20160816; b=ChtapztAYNopwEBvm/q6FEolZWjb+pYKxW5RxqdMqpyZa7nOdt0ZgQQeD8lAUZQSo4 GNiH1GmZwJegNLACK0FQZMbFbgNpNFDVjZ8mGFTcohu8xIDmhQIavLMMxnawHCHJhhls dPOCBtIDwHri9Dr4z8vWxAhUzfGzfqmB4QCJNEQ939C7F0prsFGaqbC/08KqK08iQds6 r7H+nTbHKMw9S41RJN4NmAvp5qtD9qa/goKDVOOGlbY8o3M6cvaummCWrFpljdnazPzs q7ul1hXWFFc83Kyc4/UEfxUVWfpLynymZaihtgjJK8FW4d2wVaNpbznYA38J4CbFNRdm 9Udw== 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-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=rsaFCxn5rziUK5bWxDCwwJ/J2i2SrzFnWXxKMKEi6sg=; b=Z9Xl5pD7syjLWznKCqFoczHtLpRYmB3CrR0WpZsUc0VFBJADL7MNOdmLwv/q0fb0lC XxNVJ5XetvsmrsWM2Ig/5urcgm3mvab7onex78Ul1yM9pzk9a2M/M/aCP94L3pu7SkIu C97s4i8kaSaHOWVL7r7RZFYZe9JJgt9Q6KA9SSvsVzseGSC2/9EJVM6BYBn/19I5A6k9 VaKauzWWVf9NWUv6S4ZOkP1rnxSxkmrYziMd51Gmm0ECP+Wbkl4MYTkg3x2eXkDy7jT0 lu1jElp2oFUw/ancw7dhiZOXOZMvWUU6+avUPeuwTmsOpyomQnHeHJg6bLL8FCCD4+xv VCZg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=bDisV0xi; 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 y90si9333203edy.314.2021.01.18.15.14.27; Mon, 18 Jan 2021 15:14:50 -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=bDisV0xi; 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 S1733126AbhARHuL (ORCPT + 99 others); Mon, 18 Jan 2021 02:50:11 -0500 Received: from hqnvemgate24.nvidia.com ([216.228.121.143]:8752 "EHLO hqnvemgate24.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732943AbhARHuA (ORCPT ); Mon, 18 Jan 2021 02:50:00 -0500 Received: from hqmail.nvidia.com (Not Verified[216.228.121.13]) by hqnvemgate24.nvidia.com (using TLS: TLSv1.2, AES256-SHA) id ; Sun, 17 Jan 2021 23:49:20 -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 07:49:17 +0000 Date: Mon, 18 Jan 2021 09:49:13 +0200 From: Eli Cohen To: Christian =?iso-8859-1?Q?K=F6nig?= CC: Thomas Zimmermann , , , , , dri-devel Subject: Re: Change eats memory on my server Message-ID: <20210118074913.GA39161@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> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <83f74a11-b3c0-db2e-8301-4292d60d803b@amd.com> User-Agent: Mutt/1.9.5 (bf161cf53efb) (2018-04-13) X-Originating-IP: [172.20.145.6] X-ClientProxiedBy: HQMAIL111.nvidia.com (172.20.187.18) To HQMAIL107.nvidia.com (172.20.187.13) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1610956160; bh=rsaFCxn5rziUK5bWxDCwwJ/J2i2SrzFnWXxKMKEi6sg=; h=Date:From:To:CC:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:Content-Transfer-Encoding: In-Reply-To:User-Agent:X-Originating-IP:X-ClientProxiedBy; b=bDisV0xiUrtecMDMaOm8usJy68hkpobY3zlsxcue7YHmdJdQ/cXO1k0qJn1JdnUmf wDKeQczbxf5C+tEUUEkUTFCxEx9xey6pMBvC8qD8YcHJJowAhvZ+RTpBWvL0WAeVBd aa7U9lZiq9rZ2UUqWRx2HNGSnQWeM/AOEnbWF/NPrzb0VUZPTu3Ukq+nJ8vaq7f5US Xv0TGAlsErJLGadXlT/1qxkp6mllp0bCWU3yei0QhKx1OcBmIp69NvGOXcduAkSXeR SHHQKsFd0J56TVQQe8+/zCSJJoC8U/XLyCuYJj6aDGrV8v7T8snpztCut9IJhRdLbk gaA7UA6I1W/PA== Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 18, 2021 at 08:43:12AM +0100, Christian K=F6nig wrote: > Hi Eli, >=20 > have you already tried using kmemleak? >=20 > This sounds like a leak of memory allocated using kmalloc(), so kmemleak > should be able to catch it. >=20 Hi Christian, I have the following configured but I did not see any visible complaint in dmesg. CONFIG_HAVE_DEBUG_KMEMLEAK=3Dy CONFIG_DEBUG_KMEMLEAK=3Dy CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE=3D16000 Any other configuration that I need to set?