Re: [Bugme-new] [Bug 33102] New: File's copied from client->linux server only copy 1st 64K data; rest is lost

[Andrew Morton <akpm@linux-foundation.org>]

(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Mon, 11 Apr 2011 22:12:41 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=33102
> 
>            Summary: File's copied from client->linux server only copy 1st
>                     64K data;rest is lost
>            Product: Networking
>            Version: 2.5
>     Kernel Version: 2.6.38.2
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: blocking
>           Priority: P1
>          Component: IPV4
>         AssignedTo: shemminger@linux-foundation.org
>         ReportedBy: lkml@tlinx.org
>         Regression: Yes

Seems to be a 2.6.37->2.6.38 regression.

> 
> Created an attachment (id=54112)
>  --> (https://bugzilla.kernel.org/attachment.cgi?id=54112)
> config file
> 
> I've run into a problem copying a 3.6M file from a Win7 client to
> the linux server via cifs.
> 
> 
> Under 2.6.38.2, it only copies the first 64K (exactly) and the
> client gets a write error.
> 
> Using wireshark, in the success case, after the client sends the first
> 64K, the server response with 4 acks  each advertising a Window
> size of ~48K, followed by an SMB packet acknowledging the first 64K, w/info:
>   "WRITE AndX Request, 65536 bytes".
> 
> In the fail case, the server responds with 4 acks, but in each of the
> 4 ACKS, it's advertising strange window sizes of 881, 1161, 1441 1721
> and then responds with a faulty SMB packet w/info:
>   "[TCP Retransmission] Trans2 Response<unknown>"
>  Under the Trans2 section it says:
> 
>   Subcommand: <Unknown> since request packet wasn't seen.
> 
> 
> ----
> 
> I originally upgraded from 2.6.35.7 -> 2.6.38.2 and encountered this
> prob, so successively tried the 26.35.7 config w/2.6.36, 37, 38 and finally
> 38.1 -- they all work.
> 
> The same config on 2.6.38.2 fails as described above.
> 
> 
> Config attached.
>