From: Ulrich Hecht <uli@fpond.eu>
To: iwamatsu@gmail.com
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"pavel@nabladev.com" <pavel@nabladev.com>,
"nobuhiro.iwamatsu.x90@mail.toshiba"
<nobuhiro.iwamatsu.x90@mail.toshiba>
Subject: Re: [cip-dev] Request for review for 4.19-st13, 4.19-cip129
Date: Mon, 23 Feb 2026 05:33:36 +0100 (CET) [thread overview]
Message-ID: <1825159101.48826.1771821216174@webmail.strato.de> (raw)
In-Reply-To: <CACe6DC6Lt0Y9vPfMb9NhgOg4FcMCWDaFxAR7c8oLh9rZt87SPA@mail.gmail.com>
> On 02/21/2026 6:21 AM CET Nobuhiro Iwamatsu via lists.cip-project.org <iwamatsu=gmail.com@lists.cip-project.org> wrote:
> Hi Uli,
>
> The following commit requires a fix. Enabling the driver will cause a
> build error.
>
> c85bc75effc21 fbdev: ssd1307fb: fix potential page leak in ssd1307fb_probe()
> ```
> drivers/video/fbdev/ssd1307fb.c: In function 'ssd1307fb_probe':
> drivers/video/fbdev/ssd1307fb.c:726:22: error: passing argument 1 of
> '__free_pages' from incompatible pointer type
> [-Werror=incompatible-pointer-types]
> 726 | __free_pages(vmem, get_order(vmem_size));
> | ^~~~
> | |
> | u8 * {aka unsigned char *}
> In file included from ./include/linux/idr.h:16,
> from ./include/linux/kernfs.h:14,
> from ./include/linux/sysfs.h:16,
> from ./include/linux/kobject.h:20,
> from ./include/linux/device.h:16,
> from ./include/linux/backlight.h:12,
> from drivers/video/fbdev/ssd1307fb.c:9:
> ./include/linux/gfp.h:566:39: note: expected 'struct page *' but
> argument is of type 'u8 *' {aka 'unsigned char *'} 566 | extern
> void __free_pages(struct page *page, unsigned int order);
> | ~~~~~~~~~~~~~^~~~
> ```
>
> This can be fixed by cast to vmem.
Fixed, thanks!
CU
Uli
prev parent reply other threads:[~2026-02-23 4:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 6:38 Request for review for 4.19-st13, 4.19-cip129 Ulrich Hecht
2026-02-20 22:39 ` Pavel Machek
2026-02-21 5:21 ` [cip-dev] " Nobuhiro Iwamatsu (Toshiba)
2026-02-23 4:33 ` Ulrich Hecht [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=1825159101.48826.1771821216174@webmail.strato.de \
--to=uli@fpond.eu \
--cc=cip-dev@lists.cip-project.org \
--cc=iwamatsu@gmail.com \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=pavel@nabladev.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