summaryrefslogtreecommitdiffstats
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorSudip Mukherjee2015-05-12 14:06:08 +0200
committerGreg Kroah-Hartman2015-05-24 22:35:25 +0200
commit7d98c63edc45e4ab3096af2c8d98fd2d94249640 (patch)
treea102978bf582a57e23ce7f5f07a8dff4c9af3705 /MAINTAINERS
parentstaging: sm750: Fix lynxfb_ops_imageblit() if image->depth != 1 (diff)
downloadkernel-qcow2-linux-7d98c63edc45e4ab3096af2c8d98fd2d94249640.tar.gz
kernel-qcow2-linux-7d98c63edc45e4ab3096af2c8d98fd2d94249640.tar.xz
kernel-qcow2-linux-7d98c63edc45e4ab3096af2c8d98fd2d94249640.zip
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 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions