public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Alessandro Carminati <alessandro.carminati@gmail.com>
Cc: Philip Daly <pdaly@redhat.com>,
	Michael Turquette <mturquette@baylibre.com>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Sanitize possible_parent_show to Handle Return Value of of_clk_get_parent_name
Date: Thu, 07 Sep 2023 15:33:25 -0700	[thread overview]
Message-ID: <fc8023b435f78e02c96fecbe8e7599ee.sboyd@kernel.org> (raw)
In-Reply-To: <CAPp5cGTshQJ3aLeLqv=CbaVeg9GnK_k9nsoaWrBKs1dcXzNZow@mail.gmail.com>

Quoting Alessandro Carminati (2023-09-07 07:15:36)
> this is a gentle ping
> 

I couldn't read your email because it was sent to nobody
(unlisted-recipients). Can you resend with a proper To: line? 

> 
> Il giorno mar 22 ago 2023 alle ore 15:49 Alessandro Carminati
> <alessandro.carminati@gmail.com> ha scritto:
> >
> > In the possible_parent_show function, ensure proper handling of the return
> > value from of_clk_get_parent_name to prevent potential issues arising from
> > a NULL return.
> > The current implementation invokes seq_puts directly on the result of
> > of_clk_get_parent_name without verifying the return value, which can lead
> > to kernel panic if the function returns NULL.
> >
> > This patch addresses the concern by introducing a check on the return
> > value of of_clk_get_parent_name. If the return value is not NULL, the

Use of_clk_get_parent_name() to signify that it is a function.

> > function proceeds to call seq_puts, providing the returned value as
> > argument.
> > However, if of_clk_get_parent_name returns NULL, the function provides a
> > static string as argument, avoiding the panic.
> >
> > Reported-by: Philip Daly <pdaly@redhat.com>
> > Signed-off-by: Alessandro Carminati (Red Hat) <alessandro.carminati@gmail.com>
> > ---

It needs a Fixes tag.

> >  drivers/clk/clk.c | 11 ++++++-----
> >  1 file changed, 6 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
> > index c249f9791ae8..ab999644e185 100644
> > --- a/drivers/clk/clk.c
> > +++ b/drivers/clk/clk.c
> > @@ -3416,6 +3416,7 @@ static void possible_parent_show(struct seq_file *s, struct clk_core *core,
> >                                  unsigned int i, char terminator)
> >  {
> >         struct clk_core *parent;
> > +       const char *tmp;
> >
> >         /*
> >          * Go through the following options to fetch a parent's name.
> > @@ -3436,12 +3437,12 @@ static void possible_parent_show(struct seq_file *s, struct clk_core *core,
> >                 seq_puts(s, core->parents[i].name);
> >         else if (core->parents[i].fw_name)
> >                 seq_printf(s, "<%s>(fw)", core->parents[i].fw_name);
> > -       else if (core->parents[i].index >= 0)
> > -               seq_puts(s,
> > -                        of_clk_get_parent_name(core->of_node,
> > -                                               core->parents[i].index));
> > -       else
> > +       else if (core->parents[i].index >= 0) {
> > +               tmp = of_clk_get_parent_name(core->of_node, core->parents[i].index);
> > +               seq_puts(s, tmp ? tmp : "(none)");

How about using seq_printf("%s", ...) instead? That should print out
"(null)" in the case that it is NULL, instead of "(none)" and it is a
one line change.

  reply	other threads:[~2023-09-07 22:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22 13:48 [PATCH] Sanitize possible_parent_show to Handle Return Value of of_clk_get_parent_name Alessandro Carminati
2023-09-07 14:15 ` Alessandro Carminati
2023-09-07 22:33   ` Stephen Boyd [this message]
2023-09-08  8:36     ` Alessandro Carminati
2023-09-08 21:25       ` Stephen Boyd
2023-09-12 17:05         ` Alessandro Carminati
2023-09-12 17:59           ` Stephen Boyd
2023-09-14 13:25             ` Alessandro Carminati

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=fc8023b435f78e02c96fecbe8e7599ee.sboyd@kernel.org \
    --to=sboyd@kernel.org \
    --cc=alessandro.carminati@gmail.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=pdaly@redhat.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