Received-SPF: pass (google.com: domain of linux-kernel+bounces-128996-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Message-ID: <59860bb4-0dff-4575-b4cb-b88e6e1ccb77@huawei.com>
Date: Wed, 3 Apr 2024 11:19:32 +0800
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PATCH v3 0/3] page_owner: Fix refcount imbalance
Content-Language: en-US
To: Oscar Salvador <osalvador@suse.de>
CC: Andrew Morton <akpm@linux-foundation.org>, <linux-kernel@vger.kernel.org>,
	<linux-mm@kvack.org>, Michal Hocko <mhocko@suse.com>, Vlastimil Babka
	<vbabka@suse.cz>, Marco Elver <elver@google.com>, Andrey Konovalov
	<andreyknvl@gmail.com>, Alexander Potapenko <glider@google.com>
References: <20240326063036.6242-1-osalvador@suse.de>
 <74b147b0-718d-4d50-be75-d6afc801cd24@huawei.com>
 <ZgwUP17giMgGksXc@localhost.localdomain>
From: Kefeng Wang <wangkefeng.wang@huawei.com>
In-Reply-To: <ZgwUP17giMgGksXc@localhost.localdomain>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit


On 2024/4/2 22:20, Oscar Salvador wrote:
> On Fri, Mar 29, 2024 at 12:54:30PM +0800, Kefeng Wang wrote:
>> I still see the following memory leak, could you check it?
>>
>> /mnt/arm64 # cat /sys//kernel/debug/kmemleak
>> unreferenced object 0xffff000200d91000 (size 16):
>>    comm "kworker/4:0", pid 42, jiffies 4294892753
>>    hex dump (first 16 bytes):
>>      60 37 57 c1 00 00 ff ff 00 00 00 00 00 00 00 00  `7W.............
>>    backtrace (crc 4458f477):
>>      [<(____ptrval____)>] kmemleak_alloc+0x3c/0x50
>>      [<(____ptrval____)>] kmalloc_trace+0x20c/0x2e0
>>      [<(____ptrval____)>] __set_page_owner+0x1d0/0x2a0
>>      [<(____ptrval____)>] prep_new_page+0x108/0x138
>>      [<(____ptrval____)>] get_page_from_freelist+0x79c/0x16b8
>>      [<(____ptrval____)>] __alloc_pages+0x1bc/0x440
>>      [<(____ptrval____)>] new_slab+0x104/0x3c8
>>      [<(____ptrval____)>] ___slab_alloc+0x368/0xb20
>>      [<(____ptrval____)>] __slab_alloc.isra.0+0x3c/0x88
>>      [<(____ptrval____)>] kmalloc_trace+0x280/0x2e0
>>      [<(____ptrval____)>] __set_page_owner+0x1d0/0x2a0
>>      [<(____ptrval____)>] prep_new_page+0x108/0x138
>>      [<(____ptrval____)>] get_page_from_freelist+0x79c/0x16b8
>>      [<(____ptrval____)>] __alloc_pages+0x1bc/0x440
>>      [<(____ptrval____)>] new_slab+0x104/0x3c8
>>      [<(____ptrval____)>] ___slab_alloc+0x368/0xb20
> 
> Hi Kefeng Wang
> 
> You seem to be missing [1]
> 
> Could you try with that patch applied?
> 
> [1] https://lore.kernel.org/linux-mm/20240315222610.6870-1-osalvador@suse.de/

Hi, re-run with clean v6.9-rc2 (already include 7844c0147211
mm,page_owner: fix recursion), after booting and wait some time,
the kmemleak is still occurred.


> 
> Thanks
>