Re: [RFC PATCH 0/2] Faster/parallel SYN handling to mitigate SYN floods

Eric Dumazet
2012-05-30T08:50:29Z

On Wed, 2012-05-30 at 10:44 +0200, Jesper Dangaard Brouer wrote:

> Choosing that code path, should be easy by simply returning 0 (no_limit)
> from my function tcp_v4_syn_conn_limit(), to indicate that the normal
> slow code path should be chosen.
>
> I guess this will not pose a big attack angle, as the entries in
> reqsk_queue will be fairly small.

Not sure what you mean.

I know some people have 64K entries in it.

(sk_ack_backlog / sk_max_ack_backlog being 16bits,
listen(fd, 65536 + 1) can give unexpected results)