From: Zhang Shurong <zhang_shurong@foxmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, linux-imx@nxp.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bus: imx-weim: fix to avoid potential NULL pointer dereference
Date: Mon, 28 Aug 2023 23:03:05 +0800 [thread overview]
Message-ID: <tencent_D90A6A9DC4DD4D576DDA5600188F47A2C206@qq.com> (raw)
In-Reply-To: <CAOMZO5BByJsCOCpQ9WZqMWP7qmh7x3N06wD9VhpWMjoi4hg2ag@mail.gmail.com>
在 2023年7月16日星期日 CST 上午12:38:09,Fabio Estevam 写道:
> Hi Zhang,
>
> On Sat, Jul 15, 2023 at 12:21 PM Zhang Shurong
>
> <zhang_shurong@foxmail.com> wrote:
> > of_match_device() may fail and returns a NULL pointer.
> >
> > Fix this by checking the return value of of_match_device.
> >
> > Fixes: 3f98b6baad63 ("drivers: bus: imx-weim: Add support for
> > i.MX1/21/25/27/31/35/50/51/53") Signed-off-by: Zhang Shurong
> > <zhang_shurong@foxmail.com>
> > ---
> >
> > drivers/bus/imx-weim.c | 10 +++++++---
> > 1 file changed, 7 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/bus/imx-weim.c b/drivers/bus/imx-weim.c
> > index 52a5d0447390..65402bb60c18 100644
> > --- a/drivers/bus/imx-weim.c
> > +++ b/drivers/bus/imx-weim.c
> > @@ -202,15 +202,19 @@ static int weim_timing_setup(struct device *dev,
> > struct device_node *np,>
> > static int weim_parse_dt(struct platform_device *pdev)
> > {
> >
> > - const struct of_device_id *of_id = of_match_device(weim_id_table,
> > - &pdev->dev);
> > - const struct imx_weim_devtype *devtype = of_id->data;
> > + const struct of_device_id *of_id;
> > + const struct imx_weim_devtype *devtype;
> >
> > int ret = 0, have_child = 0;
> > struct device_node *child;
> > struct weim_priv *priv;
> > void __iomem *base;
> > u32 reg;
> >
> > + of_id = of_match_device(weim_id_table, &pdev->dev);
> > + if (!of_id)
> > + return -EINVAL;
>
> If there is no match the driver will not probe in the first place.
>
> I don't think this check is needed.
Hello Fabio,
I think we can make it happen by designing the platform device in a way that
its name aligns with that of the driver. In such a scenario, when the driver
is probed, the of_match_device function will return null. You can verify this
functionality by reviewing the following function:
static int platform_match(struct device *dev, struct device_driver *drv)
Best regards,
Shurong
next prev parent reply other threads:[~2023-08-28 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 15:21 Zhang Shurong
2023-07-15 16:38 ` Fabio Estevam
2023-08-28 15:03 ` Zhang Shurong [this message]
2023-08-28 18:41 ` Fabio Estevam
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=tencent_D90A6A9DC4DD4D576DDA5600188F47A2C206@qq.com \
--to=zhang_shurong@foxmail.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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
all inboxes | Powered by JetHome®