linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Kees Cook <keescook@chromium.org>,
	Daniel Micay <danielmicay@gmail.com>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	freeze0985@gmail.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Fwd: kmalloc memory leak over time.
Date: Thu, 28 Sep 2023 15:40:31 +0700	[thread overview]
Message-ID: <4f01f302-9d59-4146-b7ff-0478c4bd94b1@gmail.com> (raw)

Hi,

I notice a regression report on Bugzilla [1]. Quoting from it:

> Since 1st weak of Sept I have been observing memory leak in my system, so after doing a little big of digging I found out that the leak is caused by kmalloc. In Linux 6.5.3 memory leak would increase  to nearly 50% of my ram over a period of 6-9 hours. In the Newer Linux 6.5.4 I am yet to observe that much memory leak(Haven't used my laptop for that long till now) but over a period of 3 hours I see 2.2GB reserved and it is not used by any program at all. this is just after 3 hours of usage on Linux 6.5.4.

Later, the reporter (Cc'ed) narrowed down the version range, with
memory statistics:

> 6.4 works fine I down graded to it before linux 6.5.4 was released. no memory leak.
> 
> today i ran my laptop for 6 hours and 40 mins and this memory leak is still happening at same rate.
> 
>               total        used        free      shared  buff/cache   available
> Mem:            15Gi       7.2Gi       2.8Gi       797Mi       6.4Gi       8.1Gi
> Swap:             0B          0B          0B
> Total:          15Gi       7.2Gi       2.8Gi

See Bugzilla for the full thread.

Anyway, I'm adding this regression to be tracked by regzbot:

#regzbot introduced: v6.4..v6.5 https://bugzilla.kernel.org/show_bug.cgi?id=217943

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217943

-- 
An old man doll... just what I always wanted! - Clara


             reply	other threads:[~2023-09-28  8:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28  8:40 Bagas Sanjaya [this message]
2023-09-28  9:39 ` Victor Fries985
2023-09-28 11:01   ` Bagas Sanjaya
2023-09-28 12:55 ` Fwd: " Linux regression tracking (Thorsten Leemhuis)
2023-10-05 14:14   ` Bagas Sanjaya

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=4f01f302-9d59-4146-b7ff-0478c4bd94b1@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=danielmicay@gmail.com \
    --cc=freeze0985@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ndesaulniers@google.com \
    --cc=regressions@lists.linux.dev \
    /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