Re: kmemleak: Cannot allocate a kmemleak_object structure - Kernel 4.19.13

[Nathan Royce]

I'm not all that sure it was memory related based on my Sun, 6 Jan
2019 13:17:04 -0600 post.
You'll see the log entries at 3AM, and based on earlier entries I
likely went to sleep around 1AM which would mean any memory intense
applications (eg. virtual machine) would've been closed out.
I have 8GB RAM in my desktop.


On Mon, Jan 7, 2019 at 3:52 AM Catalin Marinas <catalin.marinas@xxxxxxx> wrote:
>
> Hi Nathan,
>
> On Tue, Jan 01, 2019 at 01:17:06PM -0600, Nathan Royce wrote:
> > I had a leak somewhere and I was directed to look into SUnreclaim
> > which was 5.5 GB after an uptime of a little over 1 month on an 8 GB
> > system. kmalloc-2048 was a problem.
> > I just had enough and needed to find out the cause for my lagging system.
> >
> > I finally upgraded from 4.18.16 to 4.19.13 and enabled kmemleak to
> > hunt for the culprit. I don't think a day had elapsed before kmemleak
> > crashed and disabled itself.
>
> Under memory pressure, kmemleak may fail to allocate memory. See this
> patch for an attempt to slightly improve things but it's not a proper
> solution:
>
> http://lkml.kernel.org/r/20190102180619.12392-1-cai@xxxxxx
>
> --
> Catalin