All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lance Yang <lance.yang@linux.dev>
To: adam.c.preble@intel.com
Cc: linux-mm@kvack.org, Lance Yang <ioworker0@gmail.com>
Subject: Re: Accounting for vmap_area object growth when kmemleak doesn't notice any leaks
Date: Fri, 31 Oct 2025 16:46:16 +0800	[thread overview]
Message-ID: <20251031084616.64054-1-lance.yang@linux.dev> (raw)
In-Reply-To: <PH7PR11MB6523C5200943207E879FB5CAA9F8A@PH7PR11MB6523.namprd11.prod.outlook.com>

From: Lance Yang <ioworker0@gmail.com>

That's a tricky one. With kmemleak being clean, it seems like a logical leak.

Might be worth enabling CONFIG_MEM_ALLOC_PROFILING[1], which is perfect for
tracking down the call sites of allocations that are still live.

[1] https://docs.kernel.org/mm/allocation-profiling.html

Cheers,
Lance


  reply	other threads:[~2025-10-31  8:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31  2:36 Accounting for vmap_area object growth when kmemleak doesn't notice any leaks Preble, Adam C
2025-10-31  8:46 ` Lance Yang [this message]
2025-11-13  1:37   ` Preble, Adam C

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=20251031084616.64054-1-lance.yang@linux.dev \
    --to=lance.yang@linux.dev \
    --cc=adam.c.preble@intel.com \
    --cc=ioworker0@gmail.com \
    --cc=linux-mm@kvack.org \
    /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.