From: Nathan Royce <nroycea+kernel@gmail.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: kmemleak: Cannot allocate a kmemleak_object structure - Kernel 4.19.13
Date: Fri, 11 Jan 2019 01:05:41 -0600 [thread overview]
Message-ID: <CALaQ_hraox3anhupk_psorbAwyWK5wN-dHyp6bbGvQteyVWZsg@mail.gmail.com> (raw)
In-Reply-To: <20190107095229.uvfuxpglreibxlo4@mbp>
One more thought that may be nothing, but when kmemleak crashed,
SUnreclaim was at 932552 kB, and after reclaimed/cleared 299840 kB.
There weren't any performance issues like when I had a leak of 5.5 gB
in the 4.18 kernel.
On Mon, Jan 7, 2019 at 3:52 AM Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> 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@lca.pw
>
> --
> Catalin
prev parent reply other threads:[~2019-01-11 7:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 19:17 Nathan Royce
2019-01-02 1:04 ` Nathan Royce
2019-01-06 19:17 ` Nathan Royce
2019-01-07 9:52 ` Catalin Marinas
2019-01-09 4:04 ` Nathan Royce
2019-01-11 7:05 ` Nathan Royce [this message]
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=CALaQ_hraox3anhupk_psorbAwyWK5wN-dHyp6bbGvQteyVWZsg@mail.gmail.com \
--to=nroycea+kernel@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox