From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933023AbcK3L7g convert rfc822-to-8bit (ORCPT ); Wed, 30 Nov 2016 06:59:36 -0500 Received: from rtits2.realtek.com ([211.75.126.72]:52819 "EHLO rtits2.realtek.com.tw" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750708AbcK3L70 (ORCPT ); Wed, 30 Nov 2016 06:59:26 -0500 Authenticated-By: X-SpamFilter-By: BOX Solutions SpamTrap 5.56 with qID uAUBwxsT005536, This message is accepted by code: ctloc85258 From: Hayes Wang To: David Miller , "mlord@pobox.com" CC: "greg@kroah.com" , "romieu@fr.zoreil.com" , "netdev@vger.kernel.org" , nic_swsd , "linux-kernel@vger.kernel.org" , "linux-usb@vger.kernel.org" Subject: RE: [PATCH net 1/2] r8152: fix the sw rx checksum is unavailable Thread-Topic: [PATCH net 1/2] r8152: fix the sw rx checksum is unavailable Thread-Index: AQHSO+t3nHKkZLLsBUqa3CUPsCXz6KDci+AwgAAm4ICAAaIjoP//1LUAgAfJkeCAAC16gIAAmNB+///IdICAAR1zgIAAiCTw//+4SQAAAMTjgAAA+GcAAALhTwAADFMsAAAHEqSAACOgmaD//79lgP/38ohA Date: Wed, 30 Nov 2016 11:58:58 +0000 Message-ID: <0835B3720019904CB8F7AA43166CEEB201057793@RTITMBSV03.realtek.com.tw> References: <20161125095350.GA20653@kroah.com> <1816ec7e-2733-f4ba-5d30-29dbabd20aad@pobox.com> <20161125.115827.2014848246966159357.davem@davemloft.net> In-Reply-To: <20161125.115827.2014848246966159357.davem@davemloft.net> Accept-Language: zh-TW, en-US Content-Language: zh-TW X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.21.177.128] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Mark Lord [...] > > Not sure why, because there really is no other way for the data to > > appear where it does at the beginning of that URB buffer. > > > > This does seem a rather unexpected burden to place upon someone > > reporting a regression in a USB network driver that corrupts user data. > > If you are the only person who can actively reproduce this, which > seems to be the case right now, this is unfortunately the only way to > reach a proper analysis and fix. I have tested it with iperf more than five days without any error. I would think if there is any other way to reproduce it. Best Regards, Hayes