From: Jan Kara <jack@suse.cz>
To: Li Zetao <lizetao1@huawei.com>
Cc: tytso@mit.edu, jack@suse.com, yi.zhang@huawei.com,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] jbd2: Fix memory leak in journal_init_common()
Date: Mon, 11 Sep 2023 10:49:41 +0200 [thread overview]
Message-ID: <20230911084941.hlptflu2d3s3gjle@quack3> (raw)
In-Reply-To: <20230911025138.983101-1-lizetao1@huawei.com>
On Mon 11-09-23 10:51:38, Li Zetao wrote:
> There is a memory leak reported by kmemleak:
>
> unreferenced object 0xff11000105903b80 (size 64):
> comm "mount", pid 3382, jiffies 4295032021 (age 27.826s)
> hex dump (first 32 bytes):
> 04 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 ................
> ff ff ff ff 00 00 00 00 00 00 00 00 00 00 00 00 ................
> backtrace:
> [<ffffffffae86ac40>] __kmalloc_node+0x50/0x160
> [<ffffffffaf2486d8>] crypto_alloc_tfmmem.isra.0+0x38/0x110
> [<ffffffffaf2498e5>] crypto_create_tfm_node+0x85/0x2f0
> [<ffffffffaf24a92c>] crypto_alloc_tfm_node+0xfc/0x210
> [<ffffffffaedde777>] journal_init_common+0x727/0x1ad0
> [<ffffffffaede1715>] jbd2_journal_init_inode+0x2b5/0x500
> [<ffffffffaed786b5>] ext4_load_and_init_journal+0x255/0x2440
> [<ffffffffaed8b423>] ext4_fill_super+0x8823/0xa330
> ...
>
> The root cause was traced to an error handing path in journal_init_common()
> when malloc memory failed in register_shrinker(). The checksum driver is
> used to reference to checksum algorithm via cryptoapi and the user should
> release the memory when the driver is no longer needed or the journal
> initialization failed.
>
> Fix it by calling crypto_free_shash() on the "err_cleanup" error handing
> path in journal_init_common().
>
> Fixes: c30713084ba5 ("jbd2: move load_superblock() into journal_init_common()")
> Signed-off-by: Li Zetao <lizetao1@huawei.com>
Thanks for the fixup! Looks good to me. Feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> fs/jbd2/journal.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/jbd2/journal.c b/fs/jbd2/journal.c
> index 768fa05bcbed..30dec2bd2ecc 100644
> --- a/fs/jbd2/journal.c
> +++ b/fs/jbd2/journal.c
> @@ -1601,6 +1601,8 @@ static journal_t *journal_init_common(struct block_device *bdev,
>
> err_cleanup:
> percpu_counter_destroy(&journal->j_checkpoint_jh_count);
> + if (journal->j_chksum_driver)
> + crypto_free_shash(journal->j_chksum_driver);
> kfree(journal->j_wbuf);
> jbd2_journal_destroy_revoke(journal);
> journal_fail_superblock(journal);
> --
> 2.34.1
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2023-09-11 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 2:51 [PATCH] jbd2: Fix memory leak in journal_init_common() Li Zetao
2023-09-11 3:32 ` Ritesh Harjani
2023-09-11 3:35 ` Zhang Yi
2023-09-11 8:49 ` Jan Kara [this message]
2023-09-14 15:00 ` 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=20230911084941.hlptflu2d3s3gjle@quack3 \
--to=jack@suse.cz \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizetao1@huawei.com \
--cc=tytso@mit.edu \
--cc=yi.zhang@huawei.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