From: SeongJae Park <sj@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jianglei Nie <niejianglei2021@163.com>,
sj@kernel.org, akpm@linux-foundation.org, damon@lists.linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] mm/damon/reclaim: fix potential memory leak in damon_reclaim_init()
Date: Sun, 24 Jul 2022 10:15:57 +0000 [thread overview]
Message-ID: <20220724101557.3137-1-sj@kernel.org> (raw)
In-Reply-To: <YtzyXCR/OCLYRSPx@kroah.com>
Hi Jianglei and Greg,
On Sun, 24 Jul 2022 09:18:52 +0200 Greg KH <gregkh@linuxfoundation.org> wrote:
> On Sun, Jul 24, 2022 at 02:52:24PM +0800, Jianglei Nie wrote:
> > 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.
> >
> > 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>
> > ---
> > mm/damon/reclaim.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/mm/damon/reclaim.c b/mm/damon/reclaim.c
> > index 4b07c29effe9..0b3c7396cb90 100644
> > --- a/mm/damon/reclaim.c
> > +++ b/mm/damon/reclaim.c
> > @@ -441,8 +441,10 @@ static int __init damon_reclaim_init(void)
> > if (!ctx)
> > return -ENOMEM;
> >
> > - if (damon_select_ops(ctx, DAMON_OPS_PADDR))
> > + if (damon_select_ops(ctx, DAMON_OPS_PADDR)) {
> > + damon_destroy_ctx(ctx);
> > return -EINVAL;
> > + }
> >
> > ctx->callback.after_wmarks_check = damon_reclaim_after_wmarks_check;
> > ctx->callback.after_aggregation = damon_reclaim_after_aggregation;
> > --
> > 2.25.1
> >
>
> <formletter>
>
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree. Please read:
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> for how to do this properly.
>
> </formletter>
Thank you for the notice, Greg. Jianglei, please read that great document.
And Andrew already added the 'Fixes:' and 'Cc: stable@' tags in the patch when
he added[1] it in the mm tree. Hence I think this would be merged in the
appropriate stable series once it gets merged in the mainline.
[1] https://lore.kernel.org/mm-commits/20220717004946.7AD93C34114@smtp.kernel.org/
Thanks,
SJ
prev parent reply other threads:[~2022-07-24 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220724065224.2555966-1-niejianglei2021@163.com>
2022-07-24 7:18 ` [PATCH] mm/damon/reclaim: fix potential memory leak in damon_reclaim_init() Greg KH
2022-07-24 10:15 ` SeongJae Park [this message]
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=20220724101557.3137-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=niejianglei2021@163.com \
--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).