Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Carlos Llamas <cmllamas@google.com>
Cc: stable@vger.kernel.org, Qi Zheng <zhengqi.arch@bytedance.com>,
	stable <stable@kernel.org>
Subject: Re: [PATCH 4.14.y] binder: fix memory leak in binder_init()
Date: Mon, 21 Aug 2023 15:20:37 +0200	[thread overview]
Message-ID: <2023082130-mystified-entrust-3c1b@gregkh> (raw)
In-Reply-To: <20230815180521.1049900-1-cmllamas@google.com>

On Tue, Aug 15, 2023 at 06:05:21PM +0000, Carlos Llamas wrote:
> From: Qi Zheng <zhengqi.arch@bytedance.com>
> 
> commit adb9743d6a08778b78d62d16b4230346d3508986 upstream.
> 
> In binder_init(), the destruction of binder_alloc_shrinker_init() is not
> performed in the wrong path, which will cause memory leaks. So this commit
> introduces binder_alloc_shrinker_exit() and calls it in the wrong path to
> fix that.
> 
> Signed-off-by: Qi Zheng <zhengqi.arch@bytedance.com>
> Acked-by: Carlos Llamas <cmllamas@google.com>
> Fixes: f2517eb76f1f ("android: binder: Add global lru shrinker to binder")
> Cc: stable <stable@kernel.org>
> Link: https://lore.kernel.org/r/20230625154937.64316-1-qi.zheng@linux.dev
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> [cmllamas: resolved trivial merge conflicts]
> Signed-off-by: Carlos Llamas <cmllamas@google.com>

Now queued up, thanks.

greg k-h

      reply	other threads:[~2023-08-21 13:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-12 16:36 FAILED: patch "[PATCH] binder: fix memory leak in binder_init()" failed to apply to 4.14-stable tree gregkh
2023-08-15 18:05 ` [PATCH 4.14.y] binder: fix memory leak in binder_init() Carlos Llamas
2023-08-21 13:20   ` Greg Kroah-Hartman [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=2023082130-mystified-entrust-3c1b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cmllamas@google.com \
    --cc=stable@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=zhengqi.arch@bytedance.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