From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Yang Yingliang <yangyingliang@huawei.com>,
linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Cc: eddie.huang@mediatek.com, sean.wang@mediatek.com,
a.zummo@towertech.it, alexandre.belloni@bootlin.com,
lee.jones@linaro.org
Subject: Re: [PATCH] rtc: mt6397: check return value after calling platform_get_resource()
Date: Thu, 5 May 2022 16:55:14 +0200 [thread overview]
Message-ID: <977dc0eb-fb3e-85bb-43a1-929da9aef307@collabora.com> (raw)
In-Reply-To: <20220505125043.1594771-1-yangyingliang@huawei.com>
Il 05/05/22 14:50, Yang Yingliang ha scritto:
> It will cause null-ptr-deref if platform_get_resource() returns NULL,
> we need check the return value.
>
> Fixes: fc2979118f3f ("rtc: mediatek: Add MT6397 RTC driver")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
WARNING: multiple messages have this Message-ID (diff)
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Yang Yingliang <yangyingliang@huawei.com>,
linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Cc: eddie.huang@mediatek.com, sean.wang@mediatek.com,
a.zummo@towertech.it, alexandre.belloni@bootlin.com,
lee.jones@linaro.org
Subject: Re: [PATCH] rtc: mt6397: check return value after calling platform_get_resource()
Date: Thu, 5 May 2022 16:55:14 +0200 [thread overview]
Message-ID: <977dc0eb-fb3e-85bb-43a1-929da9aef307@collabora.com> (raw)
In-Reply-To: <20220505125043.1594771-1-yangyingliang@huawei.com>
Il 05/05/22 14:50, Yang Yingliang ha scritto:
> It will cause null-ptr-deref if platform_get_resource() returns NULL,
> we need check the return value.
>
> Fixes: fc2979118f3f ("rtc: mediatek: Add MT6397 RTC driver")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Yang Yingliang <yangyingliang@huawei.com>,
linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Cc: eddie.huang@mediatek.com, sean.wang@mediatek.com,
a.zummo@towertech.it, alexandre.belloni@bootlin.com,
lee.jones@linaro.org
Subject: Re: [PATCH] rtc: mt6397: check return value after calling platform_get_resource()
Date: Thu, 5 May 2022 16:55:14 +0200 [thread overview]
Message-ID: <977dc0eb-fb3e-85bb-43a1-929da9aef307@collabora.com> (raw)
In-Reply-To: <20220505125043.1594771-1-yangyingliang@huawei.com>
Il 05/05/22 14:50, Yang Yingliang ha scritto:
> It will cause null-ptr-deref if platform_get_resource() returns NULL,
> we need check the return value.
>
> Fixes: fc2979118f3f ("rtc: mediatek: Add MT6397 RTC driver")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
_______________________________________________
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:[~2022-05-05 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 12:50 [PATCH] rtc: mt6397: check return value after calling platform_get_resource() Yang Yingliang
2022-05-05 12:50 ` Yang Yingliang
2022-05-05 12:50 ` Yang Yingliang
2022-05-05 14:55 ` AngeloGioacchino Del Regno [this message]
2022-05-05 14:55 ` AngeloGioacchino Del Regno
2022-05-05 14:55 ` AngeloGioacchino Del Regno
2022-05-19 10:06 ` Alexandre Belloni
2022-05-19 10:06 ` Alexandre Belloni
2022-05-19 10:06 ` Alexandre Belloni
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=977dc0eb-fb3e-85bb-43a1-929da9aef307@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=eddie.huang@mediatek.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=sean.wang@mediatek.com \
--cc=yangyingliang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.