summaryrefslogtreecommitdiffstats
path: root/net
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2016-04-28 17:05:25 -0400
committerDavid S. Miller <davem@davemloft.net>2016-04-28 17:05:25 -0400
commit47ff58050a7449260d990ab95fafeb84be682e79 (patch)
tree465c0b98808107b3ae615b13cdc87671d7935a21 /net
parent6c76f3d2922115f4e1327a2dcce47e94453e3375 (diff)
parent1a8deec09d12c1a2946f131aa171d5e0479333de (diff)
downloadop-kernel-dev-47ff58050a7449260d990ab95fafeb84be682e79.zip
op-kernel-dev-47ff58050a7449260d990ab95fafeb84be682e79.tar.gz
Merge branch 'pegasus-sizes'
Petko Manolov says: ==================== pegasus: correct buffer & packet sizes As noticed by Lincoln Ramsay <a1291762@gmail.com> some old (usb 1.1) Pegasus based devices may actually return more bytes than the specified in the datasheet amount. That would not be a problem if the allocated space for the SKB was equal to the parameter passed to usb_fill_bulk_urb(). Some poor bugger (i really hope it was not me, but 'git blame' is useless in this case, so anyway) decided to add '+ 8' to the buffer length parameter. Sometimes the usb transfer overflows and corrupts the socket structure, leading to kernel panic. The above doesn't seem to happen for newer (Pegasus2 based) devices which did help this bug to hide for so long. The new default is to not include the CRC at the end of each received package. So far CRC has been ignored which makes no sense to do it in a first place. The patch is against v4.6-rc5 and was tested on ADM8515 device by transferring multiple gigabytes of data over a couple of days without any complaints from the kernel. Please apply it to whatever net tree you deem fit. Changes since v1: - split the patch in two parts; - corrected the subject lines; Changes since v2: - do not append CRC by default (based on a discussion with Johannes Berg); ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud