summaryrefslogtreecommitdiffstats
path: root/drivers/pinctrl/intel
diff options
context:
space:
mode:
authorStefan Agner <stefan@agner.ch>2016-10-18 14:09:15 -0700
committerLinus Walleij <linus.walleij@linaro.org>2016-10-31 21:25:15 +0100
commit9999fe5df58773489b9564467b5c8cfb364e0b80 (patch)
tree85eb4e7a1fbcd5861ae84db0bf0f0da1a25b6a3b /drivers/pinctrl/intel
parent0553d8d0b03ad58f9917460c40a2e2b680f5bfdb (diff)
downloadlinux-9999fe5df58773489b9564467b5c8cfb364e0b80.tar.gz
linux-9999fe5df58773489b9564467b5c8cfb364e0b80.tar.bz2
linux-9999fe5df58773489b9564467b5c8cfb364e0b80.zip
pinctrl: imx: reset group index on probe
Group index is incremented on every new group parsed. Since the field is part of struct imx_pinctrl_soc_info, which is typically a global variable passed by the individual pinctrl-imx.c based driver, it does not get cleared automatically when re-probing the driver. This lead imx_pinctrl_parse_functions passing a group pointer which is outside of the allocated group space on second probe and onwards. Typically this ended up in a NULL pointer dereference when accessing the name field like this: Unable to handle kernel NULL pointer dereference at virtual address 00000000 ... PC is at strcmp+0x18/0x44 LR is at imx_dt_node_to_map+0xc4/0x290 Avoid this by setting group_index to 0 on probe. This has been observed when using DEBUG_TEST_DRIVER_REMOVE. Signed-off-by: Stefan Agner <stefan@agner.ch> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'drivers/pinctrl/intel')
0 files changed, 0 insertions, 0 deletions