On Mon, 11 Sep 2023 10:51:38 +0800, 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
> ...
>
> [...]
Applied, thanks!
[1/1] jbd2: Fix memory leak in journal_init_common()
commit: 414f73db6ce825b7264cacb9407581b87da60aeb
Best regards,
--
Theodore Ts'o <tytso@xxxxxxx>
