From: der.herr@hofr.at (Nicholas Mc Guire)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: STi: at least warn if of_iomap fails
Date: Mon, 16 Jul 2018 08:46:26 +0000 [thread overview]
Message-ID: <20180716084626.GA28893@osadl.at> (raw)
In-Reply-To: <50a1ccc1-e64a-a35e-a7b5-eeb7082478e9@st.com>
On Mon, Jul 16, 2018 at 07:55:08AM +0000, Patrice CHOTARD wrote:
> Hi Nicholas
>
> On 07/12/2018 05:48 PM, Nicholas Mc Guire wrote:
> > The call to of_iomap() is unchecked but scu_enable(), which the returned
> > address is passed on to, assumes a valid mapping. If the mapping is
> > invalid this could probably lead to undefined system state so at least
> > a warning should be issued.
> >
> > Signed-off-by: Nicholas Mc Guire <hofrat@osadl.org>
> > Fixes: commit 65ebcc115889 ("ARM: sti: Add STiH415 SOC support")
> > ---
> > Problem was found by an experimental coccinelle script
> >
> > Patch was compile tested with: multi_v7_defconfig (implies
> > CONFIG_ARCH_STI=y, CONFIG_SMP=y)
> >
> > Patch is against 4.18-rc3 (localversion-next is next-20180712)
> >
> > arch/arm/mach-sti/platsmp.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/arch/arm/mach-sti/platsmp.c b/arch/arm/mach-sti/platsmp.c
> > index 231f19e..89ae76f 100644
> > --- a/arch/arm/mach-sti/platsmp.c
> > +++ b/arch/arm/mach-sti/platsmp.c
> > @@ -109,6 +109,7 @@ static void __init sti_smp_prepare_cpus(unsigned int max_cpus)
> >
> > if (np) {
> > scu_base = of_iomap(np, 0);
> > + WARN_ON(!scu_base);
> > scu_enable(scu_base);
> > of_node_put(np);
> > }
> >
>
> I should prefer to exit with an error to avoid unpredictable behavior,
> something like this is better :
>
> scu_base = of_iomap(np, 0);
> of_node_put(np);
> if (!scu_base) {
> pr_err("No SCU remap\n");
> return;
> }
>
> scu_enable(scu_base);
>
even though it would be possible to locate that then from that message
would it not be prefereable to provide the infos upfront like:
pr_err("SCU remap failed at %s:%s():%d\n",
__FILE__, __func__, __LINE__);
if that makes sense I?ll resend - or is that considered too verbouse ?
thx!
hofrat
next prev parent reply other threads:[~2018-07-16 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 15:48 [PATCH] ARM: STi: at least warn if of_iomap fails Nicholas Mc Guire
2018-07-16 7:55 ` Patrice CHOTARD
2018-07-16 8:46 ` Nicholas Mc Guire [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-13 7:14 [PATCH 0/4] ARM: imx legacy: cleanups Nicholas Mc Guire
2019-04-13 7:14 ` [PATCH] ARM: STi: at least warn if of_iomap fails Nicholas Mc Guire
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=20180716084626.GA28893@osadl.at \
--to=der.herr@hofr.at \
--cc=linux-arm-kernel@lists.infradead.org \
/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).