All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oscar Salvador <osalvador@suse.de>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
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>
Subject: Re: [PATCH v3 0/3] page_owner: Fix refcount imbalance
Date: Tue, 2 Apr 2024 16:20:47 +0200	[thread overview]
Message-ID: <ZgwUP17giMgGksXc@localhost.localdomain> (raw)
In-Reply-To: <74b147b0-718d-4d50-be75-d6afc801cd24@huawei.com>

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/

Thanks

-- 
Oscar Salvador
SUSE Labs


  reply	other threads:[~2024-04-02 14:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26  6:30 [PATCH v3 0/3] page_owner: Fix refcount imbalance Oscar Salvador
2024-03-26  6:30 ` [PATCH v3 1/3] mm,page_owner: Update metada for tail pages Oscar Salvador
2024-04-02 10:13   ` Vlastimil Babka
2024-04-02 11:19     ` Oscar Salvador
2024-03-26  6:30 ` [PATCH v3 2/3] mm,page_owner: Fix refcount imbalance Oscar Salvador
2024-03-26  6:30 ` [PATCH v3 3/3] mm,page_owner: Fix accounting of pages when migrating Oscar Salvador
2024-04-02 10:26   ` Vlastimil Babka
2024-04-02 11:22     ` Oscar Salvador
2024-04-02 12:39       ` Vlastimil Babka
2024-03-29  4:54 ` [PATCH v3 0/3] page_owner: Fix refcount imbalance Kefeng Wang
2024-04-02 14:20   ` Oscar Salvador [this message]
2024-04-03  3:19     ` Kefeng Wang
2024-03-29  6:39 ` Alexandre Ghiti
2024-04-04 22:56   ` Palmer Dabbelt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZgwUP17giMgGksXc@localhost.localdomain \
    --to=osalvador@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@gmail.com \
    --cc=elver@google.com \
    --cc=glider@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=vbabka@suse.cz \
    --cc=wangkefeng.wang@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.