All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Elver <elver@google.com>
To: Will Deacon <will@kernel.org>, Yee Lee <yee.lee@mediatek.com>
Cc: Max Schulze <max.schulze@online.de>,
	linux-arm-kernel@lists.infradead.org,  catalin.marinas@arm.com,
	naush@raspberrypi.com, glider@google.com,  dvyukov@google.com,
	kasan-dev@googlegroups.com
Subject: Re: kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) [RPi CM4]
Date: Mon, 15 Aug 2022 17:50:18 +0200	[thread overview]
Message-ID: <CANpmjNPrDW5FRf3PdzAUsjEtHgaWVTJ2CNr0=e732fEUf4FTmQ@mail.gmail.com> (raw)
In-Reply-To: <20220815124705.GA9950@willie-the-truck>

On Mon, 15 Aug 2022 at 14:47, Will Deacon <will@kernel.org> wrote:
>
> [+kfence folks as kfence_alloc_pool() is starting the stacktrace]
>
> On Mon, Aug 15, 2022 at 11:52:05AM +0200, Max Schulze wrote:
> > Hello,
> >
> > I get these messages when booting 5.19.0 on RaspberryPi CM4.
> >
> > Full boot log is at https://pastebin.ubuntu.com/p/mVhgBwxqPj/
> >
> > Anyone seen this? What can I do ?

I think the kmemleak_ignore_phys() in [1] is wrong. It probably wants
to be a kmemleak_free_part_phys().

[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/mm/kfence?h=v5.19&id=07313a2b29ed1079eaa7722624544b97b3ead84b

+Cc Yee

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-08-15 16:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15  9:52 kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) [RPi CM4] Max Schulze
2022-08-15 12:47 ` Will Deacon
2022-08-15 15:50   ` Marco Elver [this message]
2022-08-16 10:52     ` Yee Lee (李建誼)
2022-08-16 14:26       ` Will Deacon
2022-08-16 14:34         ` Marco Elver
2022-08-16 15:31           ` Catalin Marinas
2022-08-16 15:46             ` Marco Elver
2022-08-16 15:53               ` Catalin Marinas
2022-08-16 23:39         ` Andrew Morton
2022-08-17  6:25           ` Greg Kroah-Hartman
2022-08-17  8:23             ` Catalin Marinas
2022-08-17 15:01               ` Marco Elver
2022-08-17 16:52                 ` Greg Kroah-Hartman
2022-08-17 17:02                   ` Catalin Marinas
2022-08-17 17:23                     ` Greg Kroah-Hartman

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='CANpmjNPrDW5FRf3PdzAUsjEtHgaWVTJ2CNr0=e732fEUf4FTmQ@mail.gmail.com' \
    --to=elver@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=dvyukov@google.com \
    --cc=glider@google.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=max.schulze@online.de \
    --cc=naush@raspberrypi.com \
    --cc=will@kernel.org \
    --cc=yee.lee@mediatek.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.