public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlos Llamas <cmllamas@google.com>
To: Qi Zheng <qi.zheng@linux.dev>
Cc: gregkh@linuxfoundation.org, arve@android.com, tkjos@android.com,
	maco@android.com, joel@joelfernandes.org, brauner@kernel.org,
	surenb@google.com, linux-kernel@vger.kernel.org,
	Qi Zheng <zhengqi.arch@bytedance.com>
Subject: Re: [PATCH] binder: fix memory leak in binder_init()
Date: Sun, 25 Jun 2023 16:16:28 +0000	[thread overview]
Message-ID: <ZJhoXDpX0tOWI01M@google.com> (raw)
In-Reply-To: <20230625154937.64316-1-qi.zheng@linux.dev>

On Sun, Jun 25, 2023 at 03:49:37PM +0000, Qi Zheng wrote:
> From: Qi Zheng <zhengqi.arch@bytedance.com>
> 
> 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>
> ---
>  drivers/android/binder.c       | 1 +
>  drivers/android/binder_alloc.c | 6 ++++++
>  drivers/android/binder_alloc.h | 1 +
>  3 files changed, 8 insertions(+)
> 
> diff --git a/drivers/android/binder.c b/drivers/android/binder.c
> index 486c8271cab7..d720f93d8b19 100644
> --- a/drivers/android/binder.c
> +++ b/drivers/android/binder.c
> @@ -6617,6 +6617,7 @@ static int __init binder_init(void)
>  
>  err_alloc_device_names_failed:
>  	debugfs_remove_recursive(binder_debugfs_dir_entry_root);
> +	binder_alloc_shrinker_exit();
>  
>  	return ret;
>  }
> diff --git a/drivers/android/binder_alloc.c b/drivers/android/binder_alloc.c
> index 662a2a2e2e84..e3db8297095a 100644
> --- a/drivers/android/binder_alloc.c
> +++ b/drivers/android/binder_alloc.c
> @@ -1087,6 +1087,12 @@ int binder_alloc_shrinker_init(void)
>  	return ret;
>  }
>  
> +void binder_alloc_shrinker_exit(void)
> +{
> +	unregister_shrinker(&binder_shrinker);
> +	list_lru_destroy(&binder_alloc_lru);
> +}
> +
>  /**
>   * check_buffer() - verify that buffer/offset is safe to access
>   * @alloc: binder_alloc for this proc
> diff --git a/drivers/android/binder_alloc.h b/drivers/android/binder_alloc.h
> index 138d1d5af9ce..dc1e2b01dd64 100644
> --- a/drivers/android/binder_alloc.h
> +++ b/drivers/android/binder_alloc.h
> @@ -129,6 +129,7 @@ extern struct binder_buffer *binder_alloc_new_buf(struct binder_alloc *alloc,
>  						  int pid);
>  extern void binder_alloc_init(struct binder_alloc *alloc);
>  extern int binder_alloc_shrinker_init(void);
> +extern void binder_alloc_shrinker_exit(void);
>  extern void binder_alloc_vma_close(struct binder_alloc *alloc);
>  extern struct binder_buffer *
>  binder_alloc_prepare_to_free(struct binder_alloc *alloc,
> -- 
> 2.30.2
> 

Thanks for the fix Qi Zheng.

Acked-by: Carlos Llamas <cmllamas@google.com>

  reply	other threads:[~2023-06-25 16:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-25 15:49 [PATCH] binder: fix memory leak in binder_init() Qi Zheng
2023-06-25 16:16 ` Carlos Llamas [this message]
2023-07-21  9:28   ` Qi Zheng
2023-06-26  1:47 ` Qi Zheng

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=ZJhoXDpX0tOWI01M@google.com \
    --to=cmllamas@google.com \
    --cc=arve@android.com \
    --cc=brauner@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maco@android.com \
    --cc=qi.zheng@linux.dev \
    --cc=surenb@google.com \
    --cc=tkjos@android.com \
    --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