diff options
author | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2016-02-20 14:19:34 -0800 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2016-04-20 15:42:17 +0900 |
commit | 4b59a38da5983852008270e81140f611df6f0bfd (patch) | |
tree | c6201f361f51170093e22370c7914ae22fb6f413 /include/linux/isapnp.h | |
parent | 0d8c1f17e86919fbc645ae9283304738476dd67c (diff) | |
download | lwn-4b59a38da5983852008270e81140f611df6f0bfd.tar.gz lwn-4b59a38da5983852008270e81140f611df6f0bfd.zip |
Revert "usb: hub: do not clear BOS field during reset device"
commit e5bdfd50d6f76077bf8441d130c606229e100d40 upstream.
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>
Cc: Roger Quadros <rogerq@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'include/linux/isapnp.h')
0 files changed, 0 insertions, 0 deletions