There's a new TCP regression in latest -git that triggers in randconfig testing. With the attached config i'm getting tons of these messages: [ 32.751209] TCP: too many of orphaned sockets [ 37.198307] TCP: too many of orphaned sockets [ 42.464404] TCP: too many of orphaned sockets [ 48.920392] TCP: too many of orphaned sockets [ 56.370026] TCP: too many of orphaned sockets [ 64.605937] TCP: too many of orphaned sockets and it's not possible to ssh into the testbox, the TCP connection hangs. Before i put more effort into debugging this, is this bug already known/fixed? NOTE: the .config is randconfig generated so it might have a few weird combinations of config options. One such thing i noticed is !CONFIG_BUG, this produces at least one of the following build warnings in the networking code: net/core/ethtool.c:211:1: warning: control reaches end of non-void function [-Wreturn-type] net/core/dev.c:1892:33: warning: unused variable ‘null_features’ [-Wunused-variable] net/packet/af_packet.c:1878:30: warning: ‘hdrlen’ may be used uninitialized in this function [-Wmaybe-uninitialized] net/xfrm/xfrm_policy.c:2456:17: warning: ‘xfrm_dst_ops’ may be used uninitialized in this function [-Wmaybe-uninitialized] net/xfrm/xfrm_policy.c:1351:7: warning: ‘dst_ops’ may be used uninitialized in this function [-Wmaybe-uninitialized] net/xfrm/xfrm_policy.c:1333:18: note: ‘dst_ops’ was declared here net/xfrm/xfrm_policy.c:1351:7: warning: ‘dst_ops’ may be used uninitialized in this function [-Wmaybe-uninitialized] net/xfrm/xfrm_policy.c:1333:18: note: ‘dst_ops’ was declared here Note#2, the message should probably be fixed as well: - TCP: too many of orphaned sockets + TCP: too many orphaned sockets Thanks, Ingo