From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Lucas Costa <2000.costalucas@gmail.com>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Teddy Wang <teddy.wang@siliconmotion.com>,
linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: sm750fb: free cmap on framebuffer release
Date: Tue, 22 Sep 2026 07:41:25 +0200 [thread overview]
Message-ID: <2026092214-corset-unaligned-2cb2@gregkh> (raw)
In-Reply-To: <20260922035302.167378-1-2000.costalucas@gmail.com>
On Tue, Sep 22, 2026 at 12:53:02AM -0300, Lucas Costa wrote:
> The driver never calls fb_dealloc_cmap() after it has been allocated,
> so when the buffer is torn down we leak.
>
> This happens on every unbind, and when an error is detected in
> sm750fb_framebuffer_alloc().
>
> fb_dealloc_cmap() gets called before framebuffer_release() in both places.
>
> Fixes: 81dee67e215b ("staging: sm750fb: add sm750 to staging")
>
> Signed-off-by: Lucas Costa <2000.costalucas@gmail.com>
> ---
> drivers/staging/sm750fb/sm750.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/staging/sm750fb/sm750.c b/drivers/staging/sm750fb/sm750.c
> index 8b93bfeb217b..92412534239c 100644
> --- a/drivers/staging/sm750fb/sm750.c
> +++ b/drivers/staging/sm750fb/sm750.c
> @@ -910,6 +910,7 @@ static void sm750fb_framebuffer_release(struct sm750_dev *sm750_dev)
> while (sm750_dev->fb_count) {
> fb_info = sm750_dev->fbinfo[sm750_dev->fb_count - 1];
> unregister_framebuffer(fb_info);
> + fb_dealloc_cmap(&fb_info->cmap);
> framebuffer_release(fb_info);
> sm750_dev->fb_count--;
> }
> @@ -943,6 +944,7 @@ static int sm750fb_framebuffer_alloc(struct sm750_dev *sm750_dev, int fbidx)
> return 0;
>
> release_fb:
> + fb_dealloc_cmap(&fb_info->cmap);
> framebuffer_release(fb_info);
> return err;
> }
> --
> 2.43.0
>
>
Nice, how was this found and tested?
thanks,
greg k-h
next prev parent reply other threads:[~2026-09-22 5:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 3:53 Lucas Costa
2026-09-22 5:41 ` Greg Kroah-Hartman [this message]
2026-09-22 14:25 ` Lucas Costa
2026-09-22 7:22 ` Dan Carpenter
2026-09-22 14:28 ` [PATCH v2] " Lucas Costa
2026-09-22 16:06 ` Dan Carpenter
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=2026092214-corset-unaligned-2cb2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=2000.costalucas@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.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
all inboxes | Powered by JetHome®