net: Fix oops from tcp_collapse() when using splice()
authorSteven J. Magnani <steve@digidescorp.com>
Tue, 30 Mar 2010 20:56:01 +0000 (13:56 -0700)
committerDavid S. Miller <davem@davemloft.net>
Tue, 30 Mar 2010 20:56:01 +0000 (13:56 -0700)
tcp_read_sock() can have a eat skbs without immediately advancing copied_seq.
This can cause a panic in tcp_collapse() if it is called as a result
of the recv_actor dropping the socket lock.

A userspace program that splices data from a socket to either another
socket or to a file can trigger this bug.

Signed-off-by: Steven J. Magnani <steve@digidescorp.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

No differences found