linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Nathan Royce <nroycea+kernel@gmail.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: Mon, 7 Jan 2019 09:52:30 +0000	[thread overview]
Message-ID: <20190107095229.uvfuxpglreibxlo4@mbp> (raw)
In-Reply-To: <CALaQ_hpCKoLxp-0cgxw9TqPGBSzY7RhrnFZ0jGAQ11HbOZkZ3w@mail.gmail.com>

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@lca.pw

-- 
Catalin

  parent reply	other threads:[~2019-01-07  9:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01 19:17 kmemleak: Cannot allocate a kmemleak_object structure - Kernel 4.19.13 Nathan Royce
2019-01-02  1:04 ` Nathan Royce
2019-01-06 19:17   ` Nathan Royce
2019-01-07  9:52 ` Catalin Marinas [this message]
2019-01-09  4:04   ` Nathan Royce
2019-01-11  7:05   ` Nathan Royce

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=20190107095229.uvfuxpglreibxlo4@mbp \
    --to=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nroycea+kernel@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).