mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: jim.cromie@gmail.com
Cc: linux-modules@vger.kernel.org, song@kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Jason Baron <jbaron@akamai.com>,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: kmemleaks on ac3b43283923 ("module: replace module_layout with module_memory")
Date: Thu, 30 Mar 2023 23:59:59 -0700	[thread overview]
Message-ID: <ZCaE71aPvvQ/L05L@bombadil.infradead.org> (raw)
In-Reply-To: <CAJfuBxwomDagbdNP-Q6WvzcWsNY0Z2Lu2Yy5aZQ1d9W7Ka1_NQ@mail.gmail.com>

On Thu, Mar 30, 2023 at 04:45:43PM -0600, jim.cromie@gmail.com wrote:
> hi Luis, etal
> 
> kmemleak is reporting 19 leaks during boot
> 
> because the hexdumps appeared to have module-names,
> and Ive been hacking nearby, and see the same names
> every time I boot my test-vm, I needed a clearer picture
> Jason corroborated and bisected.
> 
> the 19 leaks split into 2 groups,
> 9 with names of builtin modules in the hexdump,
> all with the same backtrace
> 9 without module-names (with a shared backtrace)
> +1 wo name-ish and a separate backtrace

Song, please take a look.

Thanks for the report Jim, what kernel are you on exactly?

  Luis

  reply	other threads:[~2023-03-31  7:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 22:45 jim.cromie
2023-03-31  6:59 ` Luis Chamberlain [this message]
2023-03-31 17:08   ` jim.cromie
2023-03-31 19:12     ` Luis Chamberlain
2023-03-31 21:42       ` jim.cromie
2023-04-01  0:27   ` Song Liu
2023-04-03 20:43     ` Luis Chamberlain
2023-04-05  1:38       ` jim.cromie
2023-04-05  2:01         ` Luis Chamberlain
2023-04-06  3:14           ` jim.cromie
2023-04-06 19:53             ` Luis Chamberlain
2023-04-11 15:10       ` Catalin Marinas
2023-04-11 17:07         ` Luis Chamberlain
2023-04-11 23:00           ` Luis Chamberlain
2023-04-12  9:53             ` Catalin Marinas
2023-04-12 17:22               ` Luis Chamberlain
2023-04-03 21:10 ` Konstantin Ryabitsev
2023-04-03 21:20 ` Kernel.org Bugbot

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=ZCaE71aPvvQ/L05L@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jbaron@akamai.com \
    --cc=jim.cromie@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=song@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®