From: Felipe Balbi <balbi@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: jun.li@nxp.com, Baolin Wang <baolin.wang@linaro.org>,
Peter Chen <peter.chen@nxp.com>,
USB list <linux-usb@vger.kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>
Subject: [v2] usb: phy: mxs: Fix NULL pointer dereference on i.MX23/28
Date: Mon, 05 Mar 2018 10:51:49 +0200 [thread overview]
Message-ID: <87muzm3nx6.fsf@linux.intel.com> (raw)
Fabio Estevam <festevam@gmail.com> writes:
> Hi Felipe,
>
> On Mon, Jan 22, 2018 at 10:28 AM, Fabio Estevam <festevam@gmail.com> wrote:
>> Hi Felipe,
>>
>> On Thu, Jan 18, 2018 at 12:22 AM, Fabio Estevam <festevam@gmail.com> wrote:
>>> From: Fabio Estevam <fabio.estevam@nxp.com>
>>>
>>> Commit e93650994a95 ("usb: phy: mxs: add usb charger type detection")
>>> causes the following kernel hang on i.MX28:
>>>
>>> [ 2.207973] usbcore: registered new interface driver usb-storage
>>> [ 2.235659] Unable to handle kernel NULL pointer dereference at virtual address 00000188
>>> [ 2.244195] pgd = (ptrval)
>>> [ 2.246994] [00000188] *pgd=00000000
>>> [ 2.250676] Internal error: Oops: 5 [#1] ARM
>>> [ 2.254979] Modules linked in:
>>> [ 2.258089] CPU: 0 PID: 1 Comm: swapper Not tainted 4.15.0-rc8-next-20180117-00002-g75d5f21 #7
>>> [ 2.266724] Hardware name: Freescale MXS (Device Tree)
>>> [ 2.271921] PC is at regmap_read+0x0/0x5c
>>> [ 2.275977] LR is at mxs_phy_charger_detect+0x34/0x1dc
>>>
>>> mxs_phy_charger_detect() makes accesses to the anatop registers via regmap,
>>> however i.MX23/28 do not have such registers, which causes a NULL pointer
>>> dereference.
>>>
>>> Fix the issue by doing a NULL check on the 'regmap' pointer.
>>>
>>> Fixes: e93650994a95 ("usb: phy: mxs: add usb charger type detection")
>>> Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
>>
>> Could this one be applied to 4.15 final so that we avoid a boot
>> regression on i.MX23/28?
>
> A gentle ping.
499350865387f8b8c40a9e9453a9a7eb3cec5dc4
next reply other threads:[~2018-03-05 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 8:51 Felipe Balbi [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-14 1:50 [v2] usb: phy: mxs: Fix NULL pointer dereference on i.MX23/28 Fabio Estevam
2018-01-22 12:28 Fabio Estevam
2018-01-18 3:46 Jun Li
2018-01-18 2:28 Peter Chen
2018-01-18 2:22 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=87muzm3nx6.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=baolin.wang@linaro.org \
--cc=fabio.estevam@nxp.com \
--cc=festevam@gmail.com \
--cc=jun.li@nxp.com \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@nxp.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;
as well as URLs for NNTP newsgroup(s).