diff options
author | Sudip Mukherjee <sudipm.mukherjee@gmail.com> | 2015-05-12 15:06:08 +0300 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2015-05-24 23:35:25 +0300 |
commit | 7d98c63edc45e4ab3096af2c8d98fd2d94249640 (patch) | |
tree | a102978bf582a57e23ce7f5f07a8dff4c9af3705 /drivers/staging/Kconfig | |
parent | 288ef567ab7b43f19838afbe12b471f1ff5fdfa3 (diff) | |
download | linux-7d98c63edc45e4ab3096af2c8d98fd2d94249640.tar.xz |
staging: panel: fix stackdump
if we load the module, unload and then again try to load the module, we
will get a stackdump. In the module_exit function we are unregistering
the device and releasing the parport. So when we reach the detach
function parport is already null and the unregister_reboot_notifier()
is never called. When we again try to load the module it again tries
register_reboot_notifier() and gives us a stackdump as its earlier
registration is still not removed. It was caused by the
commit bb046fef9668 ('staging: panel: register reboot')
Fix this by moving all the unregistering and releasing in the detach
function, which should be the ideal case as the detach will be called if
we try to unregister the driver or if the parport is removed.
Fixes: bb046fef9668 ('staging: panel: register reboot')
Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/staging/Kconfig')
0 files changed, 0 insertions, 0 deletions