From: Javier Martinez Canillas <javier@dowhile0.org>
To: Hector Martin <marcan@marcan.st>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
Alyssa Rosenzweig <alyssa@rosenzweig.io>,
Pekka Paalanen <ppaalanen@gmail.com>,
devicetree@vger.kernel.org,
dri-devel <dri-devel@lists.freedesktop.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/3] of: Move simple-framebuffer device handling from simplefb to of
Date: Mon, 13 Dec 2021 12:30:33 +0100 [thread overview]
Message-ID: <CABxcv=kbR5GX3yEfqchKJPkCqpWp_oKWjG=pu7LikBwoSX8W3A@mail.gmail.com> (raw)
In-Reply-To: <63334964-d63d-7625-e46f-a6e6ec19e908@marcan.st>
On Mon, Dec 13, 2021 at 11:46 AM Hector Martin <marcan@marcan.st> wrote:
>
> On 13/12/2021 17.44, Javier Martinez Canillas wrote:
> > Hello Hector,
> >
> > On Sun, Dec 12, 2021 at 7:24 AM Hector Martin <marcan@marcan.st> wrote:
> >>
> >> This code is required for both simplefb and simpledrm, so let's move it
> >> into the OF core instead of having it as an ad-hoc initcall in the
> >> drivers.
> >>
> >> Acked-by: Thomas Zimmermann <tzimmermann@suse.de>
> >> Signed-off-by: Hector Martin <marcan@marcan.st>
> >> ---
> >> drivers/of/platform.c | 4 ++++
> >> drivers/video/fbdev/simplefb.c | 21 +--------------------
> >> 2 files changed, 5 insertions(+), 20 deletions(-)
> >>
> >
> > This is indeed a much better approach than what I suggested. I just
> > have one comment.
> >
> >> diff --git a/drivers/of/platform.c b/drivers/of/platform.c
> >> index b3faf89744aa..793350028906 100644
> >> --- a/drivers/of/platform.c
> >> +++ b/drivers/of/platform.c
> >> @@ -540,6 +540,10 @@ static int __init of_platform_default_populate_init(void)
> >> of_node_put(node);
> >> }
> >>
> >> + node = of_get_compatible_child(of_chosen, "simple-framebuffer");
> >
> > You have to check if the node variable is NULL here.
> >
> >> + of_platform_device_create(node, NULL, NULL);
> >
> > Otherwise this could lead to a NULL pointer dereference if debug
> > output is enabled (the node->full_name is printed).
>
> Where is it printed? I thought I might need a NULL check, but this code
Sorry, I misread of_amba_device_create() as
of_platform_device_create(), which uses the "%pOF" printk format
specifier [0] to print the node's full name as a debug output [1].
[0]: https://elixir.bootlin.com/linux/v5.16-rc5/source/Documentation/core-api/printk-formats.rst#L462
[1]: https://elixir.bootlin.com/linux/v5.16-rc5/source/drivers/of/platform.c#L233
> was suggested verbatim by Rob in v2 without the NULL check and digging
> through I found that the NULL codepath is safe.
>
You are right that passing NULL is a safe code path for now due the
of_device_is_available(node) check, but that seems fragile to me since
just adding a similar debug output to of_platform_device_create()
could trigger the NULL pointer dereference.
Best regards,
Javier
next prev parent reply other threads:[~2021-12-13 11:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 6:24 [PATCH v3 0/3] drm/simpledrm: Apple M1 / DT platform support fixes Hector Martin
2021-12-12 6:24 ` [PATCH v3 1/3] of: Move simple-framebuffer device handling from simplefb to of Hector Martin
2021-12-12 21:29 ` Rob Herring
2021-12-13 8:16 ` Thomas Zimmermann
2021-12-13 14:50 ` Rob Herring
2021-12-13 8:44 ` Javier Martinez Canillas
2021-12-13 10:45 ` Hector Martin
2021-12-13 11:30 ` Javier Martinez Canillas [this message]
2021-12-13 11:47 ` Hector Martin
2021-12-13 14:50 ` Rob Herring
2021-12-14 8:37 ` Javier Martinez Canillas
2021-12-12 6:24 ` [PATCH v3 2/3] drm/format-helper: Add drm_fb_xrgb8888_to_xrgb2101010_toio() Hector Martin
2021-12-13 8:15 ` Thomas Zimmermann
2021-12-12 6:24 ` [PATCH v3 3/3] drm/simpledrm: Add [AX]RGB2101010 formats Hector Martin
2021-12-15 13:29 ` [PATCH v3 0/3] drm/simpledrm: Apple M1 / DT platform support fixes Thomas Zimmermann
2021-12-16 10:13 ` Thomas Zimmermann
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='CABxcv=kbR5GX3yEfqchKJPkCqpWp_oKWjG=pu7LikBwoSX8W3A@mail.gmail.com' \
--to=javier@dowhile0.org \
--cc=airlied@linux.ie \
--cc=alyssa@rosenzweig.io \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marcan@marcan.st \
--cc=mripard@kernel.org \
--cc=ppaalanen@gmail.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).