tcp: Revert per-route SACK/DSACK/TIMESTAMP changes.

tcp: Revert per-route SACK/DSACK/TIMESTAMP changes.

It creates a regression, triggering badness for SYN_RECV
sockets, for example:

[19148.022102] Badness at net/ipv4/inet_connection_sock.c:293
[19148.022570] NIP: c02a0914 LR: c02a0904 CTR: 00000000
[19148.023035] REGS: eeecbd30 TRAP: 0700   Not tainted  (2.6.32)
[19148.023496] MSR: 00029032 <EE,ME,CE,IR,DR>  CR: 24002442  XER: 00000000
[19148.024012] TASK = eee9a820[1756] 'privoxy' THREAD: eeeca000

This is likely caused by the change in the 'estab' parameter
passed to tcp_parse_options() when invoked by the functions
in net/ipv4/tcp_minisocks.c

But even if that is fixed, the ->conn_request() changes made in
this patch series is fundamentally wrong.  They try to use the
listening socket's 'dst' to probe the route settings.  The
listening socket doesn't even have a route, and you can't
get the right route (the child request one) until much later
after we setup all of the state, and it must be done by hand.

This stuff really isn't ready, so the best thing to do is a
full revert.  This reverts the following commits:

0cd9d69c8de3d979a7542877fbcd2e02c92d5309
f07996fb786158a52f9bbc44f921765898826a57
11660b98947e50b0a18c2a77778ae4f3efd40a5e
4633f82b4439edccfa6ff68508b93527ad6995c7
b3542ac9a762565b681be57fab413714d78a6271
5788d6350180ae669b6382ecc1da48d5e4f00c3f
fe18d05ef50620d4bab9426d9f949c414666ee6e
02d720774e5b01018b25eeb1464c71299eeb1ae7

Signed-off-by: David S. Miller <davem@davemloft.net>