Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <f6fbf528-8213-e3b8-6990-9fcf9dec04d6@free.fr> <20190118143434.GE118707@arrakis.emea.arm.com>
 <b7629ecf-757c-f8b5-df83-ba83d7036b2f@free.fr> <20190119132832.GA29881@MBP.local>
 <6579db26-10ac-3fbf-1998-5b937a38f202@free.fr> <d4facdc2-0581-929f-caa2-b9efa9bd8f97@arm.com>
In-Reply-To: <d4facdc2-0581-929f-caa2-b9efa9bd8f97@arm.com>
From:   Rob Herring <robh+dt@kernel.org>
Date:   Mon, 21 Jan 2019 07:35:11 -0600
Message-ID: <CAL_JsqKFT8J6g02gxeBiTfBb_XHhp2-ZNB6DgaLPK85kNZGRig@mail.gmail.com>
Subject: Re: kmemleak panic
To:     Robin Murphy <robin.murphy@arm.com>
Cc:     Marc Gonzalez <marc.w.gonzalez@free.fr>,
        Catalin Marinas <catalin.marinas@arm.com>,
        Frank Rowand <frowand.list@gmail.com>,
        Marek Szyprowski <m.szyprowski@samsung.com>,
        Bjorn Andersson <bjorn.andersson@linaro.org>,
        Mark Rutland <mark.rutland@arm.com>,
        Arnd Bergmann <arnd@arndb.de>,
        Ard Biesheuvel <ard.biesheuvel@linaro.org>,
        Oscar Salvador <osalvador@suse.de>,
        Wei Yang <richard.weiyang@gmail.com>,
        Michal Hocko <mhocko@suse.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Sri Krishna chowdary <schowdary@nvidia.com>,
        Qian Cai <cai@lca.pw>, LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, Jan 21, 2019 at 6:19 AM Robin Murphy <robin.murphy@arm.com> wrote:
>
> On 21/01/2019 11:57, Marc Gonzalez wrote:
> [...]
> > # echo dump=0xffffffc021e00000 > /sys/kernel/debug/kmemleak
> > kmemleak: Object 0xffffffc021e00000 (size 2097152):
> > kmemleak:   comm "swapper/0", pid 0, jiffies 4294892296
> > kmemleak:   min_count = 0
> > kmemleak:   count = 0
> > kmemleak:   flags = 0x1
> > kmemleak:   checksum = 0
> > kmemleak:   backtrace:
> >       kmemleak_alloc_phys+0x48/0x60
> >       memblock_alloc_range_nid+0x8c/0xa4
> >       memblock_alloc_base_nid+0x4c/0x60
> >       __memblock_alloc_base+0x3c/0x4c
> >       early_init_dt_alloc_reserved_memory_arch+0x54/0xa4
> >       fdt_init_reserved_mem+0x308/0x3ec
> >       early_init_fdt_scan_reserved_mem+0x88/0xb0
> >       arm64_memblock_init+0x1dc/0x254
> >       setup_arch+0x1c8/0x4ec
> >       start_kernel+0x84/0x44c
> >       0xffffffffffffffff
>
> OK, so via the __va(phys) call in kmemleak_alloc_phys(), you end up with
> the linear map address of a no-map reservation, which unsurprisingly
> turns out not to be mapped. Is there a way to tell kmemleak that it
> can't scan within a particular object?

There was this patch posted[1]. I never got a reply, so it hasn't been applied.

Rob

https://patchwork.ozlabs.org/patch/995367/