From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Alexey Makhalov <amakhalov@vmware.com>
Cc: linux-ext4@vger.kernel.org, stable@vger.kernel.org,
Andreas Dilger <adilger.kernel@dilger.ca>
Subject: Re: [PATCH] ext4: fix memory leak in ext4_fill_super
Date: Fri, 21 May 2021 00:43:42 -0400 [thread overview]
Message-ID: <YKc6fidMj95TZp2w@mit.edu> (raw)
In-Reply-To: <20210428221928.38960-1-amakhalov@vmware.com>
On Wed, Apr 28, 2021 at 10:19:28PM +0000, Alexey Makhalov wrote:
> I've recently discovered that doing infinite loop of
> systemctl start <ext4_on_lvm>.mount, and
> systemctl stop <ext4_on_lvm>.mount
> linearly increases percpu allocator memory consumption.
> In several hours, it might lead to system instability by
> consuming most of the memory.
>
> Bug is not reproducible when the ext4 filesystem is on
> physical partition, but it is persistent when ext4 is on
> logical volume.
Why is this the case? It sounds like we're looking a buffer for each
mount where the block size is not 1k. It shouldn't matter whether it
is a physical partition or not.
- Ted
next prev parent reply other threads:[~2021-05-21 4:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 22:19 [PATCH] ext4: fix memory leak in ext4_fill_super Alexey Makhalov
2021-05-21 4:43 ` Theodore Y. Ts'o [this message]
2021-05-21 7:43 ` Alexey Makhalov
2021-05-21 7:55 ` [PATCH v2] " Alexey Makhalov
2021-05-21 14:29 ` [PATCH] " Theodore Y. Ts'o
2021-05-21 16:12 ` Alexey Makhalov
-- strict thread matches above, loose matches on Subject: below --
2021-04-28 17:28 Pavel Skripkin
2021-04-29 10:01 ` Vegard Nossum
2021-04-29 11:08 ` Pavel Skripkin
2021-04-29 11:33 ` Pavel Skripkin
2021-04-29 17:05 ` Theodore Ts'o
2021-04-29 19:20 ` Pavel Skripkin
2021-04-29 20:09 ` Pavel Skripkin
2021-04-29 21:41 ` Theodore Ts'o
2021-04-29 22:05 ` Pavel Skripkin
2021-04-30 3:44 ` Theodore Ts'o
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=YKc6fidMj95TZp2w@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=amakhalov@vmware.com \
--cc=linux-ext4@vger.kernel.org \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).