tcp: len check is unnecessarily devastating, change to WARN_ON
commit21fdc47e2e3238412559703663e5a04cbebb4309
authorIlpo Järvinen <ilpo.jarvinen@helsinki.fi>
Sat, 2 Apr 2011 04:47:41 +0000 (1 21:47 -0700)
committerGreg Kroah-Hartman <gregkh@suse.de>
Fri, 3 Jun 2011 01:33:59 +0000 (3 10:33 +0900)
treef0606b221f240d89b198ddea99d64ee034c38c98
parent29ad44a2c7365a4094772be7bbc81aff279295fc
tcp: len check is unnecessarily devastating, change to WARN_ON

[ Upstream commit 2fceec13375e5d98ef033c6b0ee03943fc460950 ]

All callers are prepared for alloc failures anyway, so this error
can safely be boomeranged to the callers domain without super
bad consequences. ...At worst the connection might go into a state
where each RTO tries to (unsuccessfully) re-fragment with such
a mis-sized value and eventually dies.

Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
net/ipv4/tcp_output.c