summaryrefslogtreecommitdiffstats
path: root/block/bounce.c
diff options
context:
space:
mode:
authorGreg Kroah-Hartman <gregkh@linuxfoundation.org>2016-02-20 14:19:34 -0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2016-02-20 14:19:34 -0800
commite5bdfd50d6f76077bf8441d130c606229e100d40 (patch)
tree21f50b8810fb5077c9fe5cf08f65ff7d4e1cfea9 /block/bounce.c
parentf9a96d2e7e46ed1ece71cf5b34ad9fe2492bacc5 (diff)
downloadlinux-stable-e5bdfd50d6f76077bf8441d130c606229e100d40.tar.gz
linux-stable-e5bdfd50d6f76077bf8441d130c606229e100d40.tar.bz2
linux-stable-e5bdfd50d6f76077bf8441d130c606229e100d40.zip
Revert "usb: hub: do not clear BOS field during reset device"
This reverts commit d8f00cd685f5c8e0def8593e520a7fef12c22407. Tony writes: This upstream commit is causing an oops: d8f00cd685f5 ("usb: hub: do not clear BOS field during reset device") This patch has already been included in several -stable kernels. Here are the affected kernels: 4.5.0-rc4 (current git) 4.4.2 4.3.6 (currently in review) 4.1.18 3.18.27 3.14.61 How to reproduce the problem: Boot kernel with slub debugging enabled (otherwise memory corruption will cause random oopses later instead of immediately) Plug in USB 3.0 disk to xhci USB 3.0 port dd if=/dev/sdc of=/dev/null bs=65536 (where /dev/sdc is the USB 3.0 disk) Unplug USB cable while dd is still going Oops is immediate: Reported-by: Tony Battersby <tonyb@cybernetics.com> Cc: Du, Changbin <changbin.du@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'block/bounce.c')
0 files changed, 0 insertions, 0 deletions