[Bug 263062] tcp_inpcb leaking in VM environment
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 24 Sep 2022 18:40:22 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263062 --- Comment #2 from Eugene M. Zheganin <eugene@zhegan.in> --- Same stuff happends with udp_inpcb: [zone: udp_inpcb] kern.ipc.maxsockets limit reached [zone: udp_inpcb] kern.ipc.maxsockets limit reached [zone: udp_inpcb] kern.ipc.maxsockets limit reached [zone: udp_inpcb] kern.ipc.maxsockets limit reached [zone: udp_inpcb] kern.ipc.maxsockets limit reached [zone: udp_inpcb] kern.ipc.maxsockets limit reached [zone: udp_inpcb] kern.ipc.maxsockets limit reached [zone: udp_inpcb] kern.ipc.maxsockets limit reached [zone: udp_inpcb] kern.ipc.maxsockets limit reached [zone: udp_inpcb] kern.ipc.maxsockets limit reached [zone: udp_inpcb] kern.ipc.maxsockets limit reached [zone: udp_inpcb] kern.ipc.maxsockets limit reached [zone: udp_inpcb] kern.ipc.maxsockets limit reached [zone: udp_inpcb] kern.ipc.maxsockets limit reached [zone: udp_inpcb] kern.ipc.maxsockets limit reached [zone: udp_inpcb] kern.ipc.maxsockets limit reached [zone: udp_inpcb] kern.ipc.maxsockets limit reached [root@prometheus:~]# vmstat -z | egrep 'USED|inpcb' ITEM SIZE LIMIT USED FREE REQ FAILSLEEP XDOMAIN udp_inpcb: 496, 2045354, 1024072, 384, 2230019,1677781, 0, 0 tcp_inpcb: 496, 2045354, 376653, 1387, 778968, 0, 0, 0 udplite_inpcb: 496, 1022671, 0, 0, 0, 0, 0, 0 Another peculiar thing: when increasing the kern.ipc.maxsockets, it cannot be set to a value larger than kern.maxfiles, but when this issue triggers, it is already way larger (kern.ipc.maxsockets is around 1M, kern.maxfiles is around 400R). How can this even be possible ? -- You are receiving this mail because: You are the assignee for the bug.