From: Petr Mladek <pmladek@suse.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Lunn <andrew@lunn.ch>,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [PATCH] of: do not leak console options
Date: Wed, 6 Sep 2017 14:40:33 +0200 [thread overview]
Message-ID: <20170906124033.GB3143@pathway.suse.cz> (raw)
In-Reply-To: <20170827071910.GA581@tigerII.localdomain>
On Sun 2017-08-27 16:19:10, Sergey Senozhatsky wrote:
> Hello,
>
> (Cc Andrew, Grant)
>
> On (08/25/17 17:37), Rob Herring wrote:
> > On Sat, Aug 26, 2017 at 02:36:47AM +0900, Sergey Senozhatsky wrote:
> > > If add_preferred_console() returns error then we must free a
> > > copy of `of_stdout_options' that we create right before the
> > > console registration.
> > >
> > > Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> > > ---
> > > drivers/of/base.c | 11 +++++++++--
> > > 1 file changed, 9 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/of/base.c b/drivers/of/base.c
> > > index 260d33c0f26c..9fcf7011d206 100644
> > > --- a/drivers/of/base.c
> > > +++ b/drivers/of/base.c
> > > @@ -1779,10 +1779,17 @@ EXPORT_SYMBOL_GPL(of_alias_get_highest_id);
> > > */
> > > bool of_console_check(struct device_node *dn, char *name, int index)
> > > {
> > > + bool ret;
> > > + char *options;
> > > +
> > > if (!dn || dn != of_stdout || console_set_on_cmdline)
> > > return false;
> > > - return !add_preferred_console(name, index,
> > > - kstrdup(of_stdout_options, GFP_KERNEL));
> > > +
> > > + options = kstrdup(of_stdout_options, GFP_KERNEL);
> >
> > The real question is why are we doing the kstrdup in the first place.
>
> I wouldn't know :) let's find that out
>
> the patch used to pass `of_stdout_options' in v1 and v2
> https://patches.linaro.org/patch/41559/
>
> starting from v3 options are kstrdup-ed
> https://patchwork.kernel.org/patch/5398761/
I was curious. The const char * was suggested by Grant Likely,
see https://lkml.kernel.org/r/CACxGe6tQ5rWzCUcS+_fFY+rjEyua2khApAoCVKpTuJAghU=N_w@mail.gmail.com
I guess that the reason was to make the of_find_node_by_path()
API clean.
> > AFAICT, the only reason is options within the console/printk code is a
> > char * and not a const char *. I can't imagine that options need
> > modifications?
>
> as far as I can tell, ->match callback has side efects, sometimes.
I hope that the match() callbacks does not have this kind of side
effects. I think that they initialize some stuff, assign some values.
But I hope that they do not modify given strings, like console
name or options. At leats I am unable to find any place.
But I am not 100% sure.
Sigh, the console code really needs clean up.
Best Regards,
Petr
next prev parent reply other threads:[~2017-09-06 12:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 17:36 Sergey Senozhatsky
2017-08-25 22:37 ` Rob Herring
2017-08-27 7:19 ` Sergey Senozhatsky
2017-08-27 8:01 ` Sergey Senozhatsky
2017-09-06 12:40 ` Petr Mladek [this message]
2017-09-06 13:29 ` Sergey Senozhatsky
2017-09-06 15:27 ` Rob Herring
2017-09-07 9:57 ` Sergey Senozhatsky
2017-09-26 6:31 ` Sergey Senozhatsky
2017-09-26 6:25 Sergey Senozhatsky
2017-10-03 7:20 ` Petr Mladek
2017-10-13 19:48 ` Geert Uytterhoeven
2017-10-13 20:44 ` Rob Herring
2017-10-12 17:24 ` Rob Herring
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=20170906124033.GB3143@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.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®