Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 24 Sep 2022 18:40:22 +0000
From:      bugzilla-noreply@freebsd.org
To:        virtualization@FreeBSD.org
Subject:   [Bug 263062] tcp_inpcb leaking in VM environment
Message-ID:  <bug-263062-27103-9iEBwJ7Gha@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-263062-27103@https.bugs.freebsd.org/bugzilla/>
References:  <bug-263062-27103@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263062

--- 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,=20=20
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 arou=
nd
400R). How can this even be possible ?

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263062-27103-9iEBwJ7Gha>