I'm not an expert in linux network code, but from a quick look into the
sources I come to the following conclusions:
The sockets mtu must be 0.
If it is not a rather complicated bug (wrong pointer, freed memory or race),
it is may worth to insert some checks when mtu is set. In some places this
is already done (it is at least 32). Though, in some other places it is set
without a further check for mtu==0:
tcp_input.c: tcp_options
tcp_input.c: tcp_conn_request indirectly by calling tcp_options
I did not look into SYN_COOKIE stuff.
Its may worth to check in tcp_options for mtu==0 and add printk for that case.
Its maybe even good to refuse mtu=0.
But as I sad, I do not really know the code.
Wolfgang Walter
-- Veni, Vidi, VISA: I came, I saw, I did a little shopping.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/