From: Roman Gushchin <[email protected]> Date: Fri, 2 Aug 2013 18:36:40 +0400
> It's possible to assign an invalid value to the net.core.somaxconn > sysctl variable, because there is no checks at all. > > The sk_max_ack_backlog field of the sock structure is defined as > unsigned short. Therefore, the backlog argument in inet_listen() > shouldn't exceed USHRT_MAX. The backlog argument in the listen() syscall > is truncated to the somaxconn value. So, the somaxconn value shouldn't > exceed 65535 (USHRT_MAX). > Also, negative values of somaxconn are meaningless. > > before: > $ sysctl -w net.core.somaxconn=256 > net.core.somaxconn = 256 > $ sysctl -w net.core.somaxconn=65536 > net.core.somaxconn = 65536 > $ sysctl -w net.core.somaxconn=-100 > net.core.somaxconn = -100 > > after: > $ sysctl -w net.core.somaxconn=256 > net.core.somaxconn = 256 > $ sysctl -w net.core.somaxconn=65536 > error: "Invalid argument" setting key "net.core.somaxconn" > $ sysctl -w net.core.somaxconn=-100 > error: "Invalid argument" setting key "net.core.somaxconn" > > Based on a prior patch from Changli Gao. > > Signed-off-by: Roman Gushchin <[email protected]> > Reported-by: Changli Gao <[email protected]> > Suggested-by: Eric Dumazet <[email protected]> > Acked-by: Eric Dumazet <[email protected]> Applied, thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
