From: Chunfeng Yun <chunfeng.yun@mediatek.com>
To: Colin King <colin.king@canonical.com>
Cc: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
chunhui dai <chunhui.dai@mediatek.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Kishon Vijay Abraham I <kishon@ti.com>,
CK Hu <ck.hu@mediatek.com>, Vinod Koul <vkoul@kernel.org>,
linux-mediatek@lists.infradead.org,
Philipp Zabel <p.zabel@pengutronix.de>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH][next] drm/mediatek: avoid dereferencing a null hdmi_phy on an error message
Date: Tue, 8 Dec 2020 09:50:02 +0800 [thread overview]
Message-ID: <1607392202.23328.1.camel@mhfsdcap03> (raw)
In-Reply-To: <20201207150937.170435-1-colin.king@canonical.com>
On Mon, 2020-12-07 at 15:09 +0000, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Currently there is a null pointer check for hdmi_phy that implies it
> may be null, however a dev_err messages dereferences this potential null
> pointer. Avoid a null pointer dereference by only emitting the dev_err
> message if hdmi_phy is non-null. It is a moot point if the error message
> needs to be printed at all, but since this is a relatively new piece of
> code it may be useful to keep the message in for the moment in case there
> are unforseen errors that need to be reported.
>
> Addresses-Coverity: ("Dereference after null check")
> Fixes: be28b6507c46 ("drm/mediatek: separate hdmi phy to different file")
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/phy/mediatek/phy-mtk-hdmi.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/phy/mediatek/phy-mtk-hdmi.c b/drivers/phy/mediatek/phy-mtk-hdmi.c
> index c5c61f5a9ea0..5184054783c7 100644
> --- a/drivers/phy/mediatek/phy-mtk-hdmi.c
> +++ b/drivers/phy/mediatek/phy-mtk-hdmi.c
> @@ -84,8 +84,9 @@ mtk_hdmi_phy_dev_get_ops(const struct mtk_hdmi_phy *hdmi_phy)
> hdmi_phy->conf->hdmi_phy_disable_tmds)
> return &mtk_hdmi_phy_dev_ops;
>
> - dev_err(hdmi_phy->dev, "Failed to get dev ops of phy\n");
> - return NULL;
> + if (hdmi_phy)
> + dev_err(hdmi_phy->dev, "Failed to get dev ops of phy\n");
> + return NULL;
indentation: one tab before return
Thanks
> }
>
> static void mtk_hdmi_phy_clk_get_data(struct mtk_hdmi_phy *hdmi_phy,
_______________________________________________
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:[~2020-12-08 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 15:09 [PATCH][next] drm/mediatek: avoid dereferencing a null hdmi_phy on an error message Colin King
2020-12-08 1:50 ` Chunfeng Yun [this message]
2020-12-08 12:55 ` Vinod Koul
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=1607392202.23328.1.camel@mhfsdcap03 \
--to=chunfeng.yun@mediatek.com \
--cc=chunhui.dai@mediatek.com \
--cc=chunkuang.hu@kernel.org \
--cc=ck.hu@mediatek.com \
--cc=colin.king@canonical.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=vkoul@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