summaryrefslogtreecommitdiffstats
path: root/drivers/uio
diff options
context:
space:
mode:
authorAlan Stern <stern@rowland.harvard.edu>2012-05-07 17:20:06 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-05-07 21:59:02 +0200
commit5cbe61c5aff0a8ada691eb8b07dbfb55c303f640 (patch)
tree7cacf1d68cbc681faa658d0fb15e035186c79908 /drivers/uio
parentMerge tag 'dwc3-for-v3.5' of git://git.kernel.org/pub/scm/linux/kernel/git/ba... (diff)
downloadlinux-5cbe61c5aff0a8ada691eb8b07dbfb55c303f640.tar.xz
linux-5cbe61c5aff0a8ada691eb8b07dbfb55c303f640.zip
usb-serial: ftdi_sio: fix oops during autosuspend
This patch (as1550) fixes a bug in the usb-serial core that affects the ftdi_sio driver and most likely others as well. The core implements suspend and resume routines, but it doesn't store pointers to those routines in the usb_driver structures that it registers, even though it does set those drivers' supports_autosuspend flag. The end result is that when one of these devices is autosuspended, we try to call through a NULL pointer. The patch fixes the problem by setting the suspend and resume method pointers to the appropriate routines in the USB serial core, along with the supports_autosuspend field, in each driver as it is registered. This should be back-ported to all the stable kernels that have the new usb_serial_register_drivers() interface. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Reported-and-tested-by: Frank Schäfer <schaefer.frank@gmx.net> Cc: stable <stable@vger.kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/uio')
0 files changed, 0 insertions, 0 deletions