From: Pankaj Dubey <pankaj.dubey@samsung.com>
To: Li.Xiubo@freescale.com, Aisheng.Dong@freescale.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
kgene.kim@samsung.com, linux@arm.linux.org.uk, arnd@arndb.de,
naushad@samsung.com, tomasz.figa@gmail.com, joshi@samsung.com,
thomas.ab@samsung.com, vikas.sajjan@samsung.com,
chow.kim@samsung.com, lee.jones@linaro.org,
"'Boris BREZILLON'" <boris.brezillon@free-electrons.com>,
"'Geert Uytterhoeven'" <geert+renesas@glider.be>,
"'Stephen Warren'" <swarren@nvidia.com>
Subject: RE: [PATCH v3] mfd: syscon: Decouple syscon interface from platform devices
Date: Thu, 18 Sep 2014 15:10:43 +0530 [thread overview]
Message-ID: <000d01cfd324$a2db05e0$e89111a0$@samsung.com> (raw)
In-Reply-To: <1c762cb71a5245f19fdcec8266fd45b6@BY2PR0301MB0613.namprd03.prod.outlook.com>
Hi,
On September 18, 2014, Li.Xiubo wrote,
> Subject: RE: [PATCH v3] mfd: syscon: Decouple syscon interface from
platform
> devices
>
> [...]
> > > I think there should have been a check for NULL on "dev" in
> > > "regmap_get_val_endian", so that if dev pointer exist then only it
> > > makes sense to get endianness property from DT.
> > >
> > > I will suggest following fix in regmap.c for this. With following
> > > fix I tested it and it works well on linux-next also. So if you can
> > > confirm following fix is working for you then I can post this patch.
> > >
> >
> > I tested the patch work.
> > But as Xiubo pointed in another mail, it may still cause other issues.
> > Looking at regmap.c, there're still some other places using the device
> > pointer, e.g. dev_xxx debug information and some tracepoints also take
> > device pointer as parameter(not sure if it will break if dev is NULL).
> > Another thing is that if dev is NULL, we may not be able to use regmap
> > debugfs feature which seems also not as our expected.
> >
> > Maybe we could consider create device structure for each syscon
> > compatible device in syscon driver in of_syscon_register in first time
> > which seems to be reasonable.
> >
> > Regards
> > Dong Aisheng
> >
> > > --------------------------------------------
> > > Subject: [PATCH] regmap: fix NULL pointer dereference in
> > > regmap_get_val_endian
> > >
> > > Recent commits for getting reg endianess causing NULL pointer
> > > dereference if dev is passed NULL in regmap_init_mmio. This patch
> > > fixes this issue, and allows to parse reg endianess only if dev and
> > > dev->of_node exist.
> > >
> > > Signed-off-by: Pankaj Dubey <pankaj.dubey@samsung.com>
> > > ---
> > > drivers/base/regmap/regmap.c | 23 ++++++++++++++---------
> > > 1 file changed, 14 insertions(+), 9 deletions(-)
> > >
> > > diff --git a/drivers/base/regmap/regmap.c
> > > b/drivers/base/regmap/regmap.c index f2281af..455a877 100644
> > > --- a/drivers/base/regmap/regmap.c
> > > +++ b/drivers/base/regmap/regmap.c
> > > @@ -477,7 +477,7 @@ static enum regmap_endian
> > > regmap_get_val_endian(struct device *dev,
> > > const struct regmap_bus *bus,
> > > const struct regmap_config *config)
{
> > > - struct device_node *np = dev->of_node;
> > > + struct device_node *np;
>
> And the 'np' must be NULL as default.
>
> Isn't it ?
>
Yes.
Thanks,
Pankaj Dubey
> Thanks,
>
> BRs
> Xiubo
>
> > > enum regmap_endian endian;
> > >
> > > /* Retrieve the endianness specification from the regmap config */
> > > @@ -487,15 +487,20 @@ static enum regmap_endian
> > > regmap_get_val_endian(struct device *dev,
> > > if (endian != REGMAP_ENDIAN_DEFAULT)
> > > return endian;
> > >
> > > - /* Parse the device's DT node for an endianness specification */
> > > - if (of_property_read_bool(np, "big-endian"))
> > > - endian = REGMAP_ENDIAN_BIG;
> > > - else if (of_property_read_bool(np, "little-endian"))
> > > - endian = REGMAP_ENDIAN_LITTLE;
> > > + /* If the dev and dev->of_node exist try to get endianness from DT
> > > */
> > > + if (dev && dev->of_node) {
> > > + np = dev->of_node;
> > >
> > > - /* If the endianness was specified in DT, use that */
> > > - if (endian != REGMAP_ENDIAN_DEFAULT)
> > > - return endian;
> > > + /* Parse the device's DT node for an endianness
> > > specification */
> > > + if (of_property_read_bool(np, "big-endian"))
> > > + endian = REGMAP_ENDIAN_BIG;
> > > + else if (of_property_read_bool(np, "little-endian"))
> > > + endian = REGMAP_ENDIAN_LITTLE;
> > > +
> > > + /* If the endianness was specified in DT, use that */
> > > + if (endian != REGMAP_ENDIAN_DEFAULT)
> > > + return endian;
> > > + }
> > >
> > > /* Retrieve the endianness specification from the bus config */
> > > if (bus && bus->val_format_endian_default)
> > > --
> > >
> > > Thanks,
> > > Pankaj Dubey
> > >
> > > > Regards
> > > > Dong Aisheng
> > > >
> > > > >
> > > > > Thanks,
> > > > > Pankaj Dubey
> > > > >
> > > > > > Regards
> > > > > > Dong Aisheng
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > linux-arm-kernel mailing list
> > > > > > > linux-arm-kernel@lists.infradead.org
> > > > > > > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> > > > >
> > >
next prev parent reply other threads:[~2014-09-18 9:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 6:31 Pankaj Dubey
2014-09-17 8:58 ` Dong Aisheng
2014-09-17 11:20 ` Pankaj Dubey
2014-09-18 3:05 ` Dong Aisheng
2014-09-18 6:03 ` Pankaj Dubey
2014-09-18 6:33 ` Li.Xiubo
2014-09-18 7:55 ` Dong Aisheng
2014-09-18 8:58 ` Li.Xiubo
2014-09-18 9:40 ` Pankaj Dubey [this message]
2014-09-18 9:36 ` Pankaj Dubey
2014-09-18 10:05 ` Dong Aisheng
2014-09-19 3:38 ` Li.Xiubo
2014-09-19 4:19 ` Dong Aisheng
2014-09-19 5:20 ` Li.Xiubo
2014-09-19 5:46 ` Dong Aisheng
2014-09-19 9:20 ` Pankaj Dubey
2014-09-18 7:58 ` Li.Xiubo
2014-09-17 15:23 ` Arnd Bergmann
2014-09-18 3:29 ` Pankaj Dubey
2014-09-18 3:07 ` Dong Aisheng
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='000d01cfd324$a2db05e0$e89111a0$@samsung.com' \
--to=pankaj.dubey@samsung.com \
--cc=Aisheng.Dong@freescale.com \
--cc=Li.Xiubo@freescale.com \
--cc=arnd@arndb.de \
--cc=boris.brezillon@free-electrons.com \
--cc=chow.kim@samsung.com \
--cc=geert+renesas@glider.be \
--cc=joshi@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=naushad@samsung.com \
--cc=swarren@nvidia.com \
--cc=thomas.ab@samsung.com \
--cc=tomasz.figa@gmail.com \
--cc=vikas.sajjan@samsung.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®