mm/damon/reclaim: fix potential memory leak in damon_reclaim_init()
authorJianglei Nie <niejianglei2021@163.com>
Thu, 14 Jul 2022 06:37:46 +0000 (14:37 +0800)
committerakpm <akpm@linux-foundation.org>
Sat, 30 Jul 2022 01:07:15 +0000 (18:07 -0700)
commit188043c7f4f2bd662f2a55957d684fffa543e600
treecd27d171e03445fcd7271cacbf8a6f4c41e5da38
parent73b73bac90d97400e29e585c678c4d0ebfd2680d
mm/damon/reclaim: fix potential memory leak in damon_reclaim_init()

damon_reclaim_init() allocates a memory chunk for ctx with
damon_new_ctx().  When damon_select_ops() fails, ctx is not released,
which will lead to a memory leak.

We should release the ctx with damon_destroy_ctx() when damon_select_ops()
fails to fix the memory leak.

Link: https://lkml.kernel.org/r/20220714063746.2343549-1-niejianglei2021@163.com
Fixes: 4d69c3457821 ("mm/damon/reclaim: use damon_select_ops() instead of damon_{v,p}a_set_operations()")
Signed-off-by: Jianglei Nie <niejianglei2021@163.com>
Reviewed-by: SeongJae Park <sj@kernel.org>
Cc: <stable@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
mm/damon/reclaim.c