diff options
author | Jack Morgenstein <jackm@dev.mellanox.co.il> | 2017-03-19 08:55:57 (GMT) |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-05-20 12:28:38 (GMT) |
commit | ecb0ab0f89c78c1bbe8386aac875f0b60753762d (patch) | |
tree | f3199c3604fa56b5671b977e788aff79392174db /drivers/iio | |
parent | 377178321690105cd4d42b33486881843ea6f8e8 (diff) | |
download | linux-ecb0ab0f89c78c1bbe8386aac875f0b60753762d.tar.xz |
IB/core: Fix sysfs registration error flow
commit b312be3d87e4c80872cbea869e569175c5eb0f9a upstream.
The kernel commit cited below restructured ib device management
so that the device kobject is initialized in ib_alloc_device.
As part of the restructuring, the kobject is now initialized in
procedure ib_alloc_device, and is later added to the device hierarchy
in the ib_register_device call stack, in procedure
ib_device_register_sysfs (which calls device_add).
However, in the ib_device_register_sysfs error flow, if an error
occurs following the call to device_add, the cleanup procedure
device_unregister is called. This call results in the device object
being deleted -- which results in various use-after-free crashes.
The correct cleanup call is device_del -- which undoes device_add
without deleting the device object.
The device object will then (correctly) be deleted in the
ib_register_device caller's error cleanup flow, when the caller invokes
ib_dealloc_device.
Fixes: 55aeed06544f6 ("IB/core: Make ib_alloc_device init the kobject")
Signed-off-by: Jack Morgenstein <jackm@dev.mellanox.co.il>
Signed-off-by: Leon Romanovsky <leon@kernel.org>
Signed-off-by: Doug Ledford <dledford@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/iio')
0 files changed, 0 insertions, 0 deletions