From: Helge Deller <deller@gmx.de>
To: Abdun Nihaal <nihaal@cse.iitm.ac.in>,
Javier Martinez Canillas <javierm@redhat.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Andrew Morton <akpm@linux-foundation.org>,
Sebastian Siewior <bigeasy@linutronix.de>,
Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
Ondrej Zary <linux@rainbow-software.org>,
Antonino Daplas <adaplas@gmail.com>,
Paul Mundt <lethal@linux-sh.org>,
Krzysztof Helt <krzysztof.h1@wp.pl>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Michal Januszewski <spock@gentoo.org>,
Heiko Schocher <hs@denx.de>, Peter Jones <pjones@redhat.com>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 00/14] fbdev: fix various memory leaks
Date: Tue, 19 May 2026 09:11:14 +0200 [thread overview]
Message-ID: <6e6afdae-0da8-4665-a450-6431c3b3de2f@gmx.de> (raw)
In-Reply-To: <20260514-fbdev-v1-0-b3a2474fa720@cse.iitm.ac.in>
On 5/14/26 10:24, Abdun Nihaal wrote:
> This patchset fixes some memory leak issues present in fbdev drivers.
>
> Since commit 56c134f7f1b5 ("fbdev: Track deferred-I/O pages in pageref struct")
> fb_deferred_io_init() allocated memory for pagerefs and returned an
> error code, but the existing drivers which call fb_deferred_io_init()
> were not updated to do cleanup. The first three commits address this.
> - fbdev: hecubafb: fix potential memory leak in hecubafb_probe()
> - fbdev: broadsheetfb: fix potential memory leak in broadsheetfb_probe()
> - fbdev: metronomefb: fix potential memory leak in metronomefb_probe()
>
> Probe functions that call fb_add_videomode() or fb_videomode_to_modelist()
> sometimes did not call fb_destry_modelist() to free the allocated
> memory. The following patches address this issue.
> - fbdev: radeon: fix potential memory leak in radeonfb_pci_register()
> - fbdev: carminefb: fix potential memory leak in alloc_carmine_fb()
> - fbdev: i740fb: fix potential memory leak in i740fb_probe()
> - fbdev: nvidia: fix potential memory leak in nvidiafb_probe()
> - fbdev: s3fb: fix potential memory leak in s3_pci_probe()
> - fbdev: tdfxfb: fix potential memory leak in tdfxfb_probe()
> - fbdev: tridentfb: fix potential memory leak in trident_pci_probe()
> - fbdev: uvesafb: fix potential memory leak in uvesafb_probe()
>
> Since commit 73ce73c30ba9 ("fbdev: Transfer video= option strings to caller; clarify ownership")
> the fb_get_options() function transfers ownership of the memory
> allocated for options, and so the caller is expected to free it. The
> following two patches address this issue.
> - fbdev: efifb: fix memory leak in efifb_probe()
> - fbdev: vesafb: fix memory leak in vesafb_probe()
>
> The following commit fixes a simple memory leak.
> - fbdev: sm501fb: fix potential memory leak in sm501fb_probe()
>
> All the patches were only compile tested.
> The issues were found using static analysis.
>
> Signed-off-by: Abdun Nihaal <nihaal@cse.iitm.ac.in>
> ---
> Abdun Nihaal (14):
> fbdev: hecubafb: fix potential memory leak in hecubafb_probe()
> fbdev: broadsheetfb: fix potential memory leak in broadsheetfb_probe()
> fbdev: metronomefb: fix potential memory leak in metronomefb_probe()
> fbdev: radeon: fix potential memory leak in radeonfb_pci_register()
> fbdev: carminefb: fix potential memory leak in alloc_carmine_fb()
> fbdev: i740fb: fix potential memory leak in i740fb_probe()
> fbdev: nvidia: fix potential memory leak in nvidiafb_probe()
> fbdev: s3fb: fix potential memory leak in s3_pci_probe()
> fbdev: tdfxfb: fix potential memory leak in tdfxfb_probe()
> fbdev: tridentfb: fix potential memory leak in trident_pci_probe()
> fbdev: uvesafb: fix potential memory leak in uvesafb_probe()
> fbdev: efifb: fix memory leak in efifb_probe()
> fbdev: vesafb: fix memory leak in vesafb_probe()
> fbdev: sm501fb: fix potential memory leak in sm501fb_probe()
>
> drivers/video/fbdev/aty/radeon_base.c | 1 +
> drivers/video/fbdev/broadsheetfb.c | 8 ++++++--
> drivers/video/fbdev/carminefb.c | 1 +
> drivers/video/fbdev/efifb.c | 1 +
> drivers/video/fbdev/hecubafb.c | 6 +++++-
> drivers/video/fbdev/i740fb.c | 1 +
> drivers/video/fbdev/metronomefb.c | 8 ++++++--
> drivers/video/fbdev/nvidia/nvidia.c | 1 +
> drivers/video/fbdev/s3fb.c | 1 +
> drivers/video/fbdev/sm501fb.c | 3 +++
> drivers/video/fbdev/tdfxfb.c | 1 +
> drivers/video/fbdev/tridentfb.c | 1 +
> drivers/video/fbdev/uvesafb.c | 4 ++--
> drivers/video/fbdev/vesafb.c | 1 +
> 14 files changed, 31 insertions(+), 7 deletions(-)
I applied the whole series to the fbdev git tree.
Thanks a lot !
Helge
prev parent reply other threads:[~2026-05-19 7:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 8:24 Abdun Nihaal
2026-05-14 8:24 ` [PATCH 01/14] fbdev: hecubafb: fix potential memory leak in hecubafb_probe() Abdun Nihaal
2026-05-15 7:57 ` Thomas Zimmermann
2026-05-14 8:24 ` [PATCH 02/14] fbdev: broadsheetfb: fix potential memory leak in broadsheetfb_probe() Abdun Nihaal
2026-05-15 7:56 ` Thomas Zimmermann
2026-05-14 8:24 ` [PATCH 03/14] fbdev: metronomefb: fix potential memory leak in metronomefb_probe() Abdun Nihaal
2026-05-15 7:18 ` Thomas Zimmermann
2026-05-14 8:24 ` [PATCH 04/14] fbdev: radeon: fix potential memory leak in radeonfb_pci_register() Abdun Nihaal
2026-05-14 8:24 ` [PATCH 05/14] fbdev: carminefb: fix potential memory leak in alloc_carmine_fb() Abdun Nihaal
2026-05-14 8:24 ` [PATCH 06/14] fbdev: i740fb: fix potential memory leak in i740fb_probe() Abdun Nihaal
2026-05-14 8:24 ` [PATCH 07/14] fbdev: nvidia: fix potential memory leak in nvidiafb_probe() Abdun Nihaal
2026-05-14 8:24 ` [PATCH 08/14] fbdev: s3fb: fix potential memory leak in s3_pci_probe() Abdun Nihaal
2026-05-14 8:24 ` [PATCH 09/14] fbdev: tdfxfb: fix potential memory leak in tdfxfb_probe() Abdun Nihaal
2026-05-14 8:24 ` [PATCH 10/14] fbdev: tridentfb: fix potential memory leak in trident_pci_probe() Abdun Nihaal
2026-05-14 8:24 ` [PATCH 11/14] fbdev: uvesafb: fix potential memory leak in uvesafb_probe() Abdun Nihaal
2026-05-14 8:24 ` [PATCH 12/14] fbdev: efifb: fix memory leak in efifb_probe() Abdun Nihaal
2026-05-15 7:16 ` Thomas Zimmermann
2026-05-14 8:24 ` [PATCH 13/14] fbdev: vesafb: fix memory leak in vesafb_probe() Abdun Nihaal
2026-05-15 7:17 ` Thomas Zimmermann
2026-05-14 8:24 ` [PATCH 14/14] fbdev: sm501fb: fix potential memory leak in sm501fb_probe() Abdun Nihaal
2026-05-19 7:11 ` Helge Deller [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=6e6afdae-0da8-4665-a450-6431c3b3de2f@gmx.de \
--to=deller@gmx.de \
--cc=FlorianSchandinat@gmx.de \
--cc=adaplas@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=bigeasy@linutronix.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=hs@denx.de \
--cc=javierm@redhat.com \
--cc=krzysztof.h1@wp.pl \
--cc=lethal@linux-sh.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=nihaal@cse.iitm.ac.in \
--cc=pjones@redhat.com \
--cc=spock@gentoo.org \
--cc=stable@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
--cc=tzimmermann@suse.de \
/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®