gpio: use kzalloc to allocate gpio_device

The use of kmalloc() to allocate the gpio_device leaves the contained struct
device object in an unknown state.  Calling dev_set_name() on a struct device
of unknown state can trigger the free() of an invalid pointer, as seen in the
following backtrace (collected by Tony Lindgren):

  kfree
  kobject_set_name_vargs
  dev_set_name
  gpiochip_add_data
  omap_gpio_probe
  platform_drv_probe
  ...

Reported-by: Geert Uytterhoeven <[email protected]>
Reported-by: Michael Welling <[email protected]>
Reported-by: Tony Lindgren <[email protected]>
Tested-by: Michael Welling <[email protected]>
Tested-by: Tony Lindgren <[email protected]>
Signed-off-by: Josh Cartwright <[email protected]>
Signed-off-by: Linus Walleij <[email protected]>

0 files changed, 0 insertions, 0 deletions