From: Jakub Sitnicki <jakub@cloudflare.com> Date: 2021-07-13 07:44:06
Proc socket stats use sk_prot->inuse_idx value to record inuse sock stats.
We currently do not set this correctly from sockmap side. The result is
reading sock stats '/proc/net/sockstat' gives incorrect values. The
socket counter is incremented correctly, but because we don't set the
counter correctly when we replace sk_prot we may omit the decrement.
To get the correct inuse_idx value move the core_initcall that initializes
the udp proto handlers to late_initcall. This way it is initialized after
UDP has the chance to assign the inuse_idx value from the register protocol
handler.
Fixes: 5e21bb4e8125 ("bpf, test: fix NULL pointer dereference on invalid expected_attach_type")
Signed-off-by: Jakub Sitnicki <jakub@cloudflare.com>
---
Missing bit from John's fix [1].
[1] https://lore.kernel.org/bpf/20210712195546.423990-1-john.fastabend@gmail.com/T/#mba9e0b6aa8dd0c01d7421a084c62ec93c9eea764
net/ipv4/udp_bpf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: John Fastabend <john.fastabend@gmail.com> Date: 2021-07-14 00:28:51
Jakub Sitnicki wrote:
Proc socket stats use sk_prot->inuse_idx value to record inuse sock stats.
We currently do not set this correctly from sockmap side. The result is
reading sock stats '/proc/net/sockstat' gives incorrect values. The
socket counter is incremented correctly, but because we don't set the
counter correctly when we replace sk_prot we may omit the decrement.
To get the correct inuse_idx value move the core_initcall that initializes
the udp proto handlers to late_initcall. This way it is initialized after
UDP has the chance to assign the inuse_idx value from the register protocol
handler.
Fixes: 5e21bb4e8125 ("bpf, test: fix NULL pointer dereference on invalid expected_attach_type")
Signed-off-by: Jakub Sitnicki <jakub@cloudflare.com>
---
Missing bit from John's fix [1].
[1] https://lore.kernel.org/bpf/20210712195546.423990-1-john.fastabend@gmail.com/T/#mba9e0b6aa8dd0c01d7421a084c62ec93c9eea764
Yep. Thanks.
Acked-by: John Fastabend <john.fastabend@gmail.com>
From: Cong Wang <hidden> Date: 2021-07-14 00:52:06
On Tue, Jul 13, 2021 at 12:44 AM Jakub Sitnicki [off-list ref] wrote:
Proc socket stats use sk_prot->inuse_idx value to record inuse sock stats.
We currently do not set this correctly from sockmap side. The result is
reading sock stats '/proc/net/sockstat' gives incorrect values. The
socket counter is incremented correctly, but because we don't set the
counter correctly when we replace sk_prot we may omit the decrement.
To get the correct inuse_idx value move the core_initcall that initializes
the udp proto handlers to late_initcall. This way it is initialized after
UDP has the chance to assign the inuse_idx value from the register protocol
handler.
Interesting. What about IPv6 module? Based on my understanding, it should
always be loaded before we can trigger udp_bpf_check_v6_needs_rebuild().
If so, your patch is complete.
From: Jakub Sitnicki <jakub@cloudflare.com> Date: 2021-07-14 15:56:35
On Wed, Jul 14, 2021 at 02:51 AM CEST, Cong Wang wrote:
On Tue, Jul 13, 2021 at 12:44 AM Jakub Sitnicki [off-list ref] wrote:
quoted
Proc socket stats use sk_prot->inuse_idx value to record inuse sock stats.
We currently do not set this correctly from sockmap side. The result is
reading sock stats '/proc/net/sockstat' gives incorrect values. The
socket counter is incremented correctly, but because we don't set the
counter correctly when we replace sk_prot we may omit the decrement.
To get the correct inuse_idx value move the core_initcall that initializes
the udp proto handlers to late_initcall. This way it is initialized after
UDP has the chance to assign the inuse_idx value from the register protocol
handler.
Interesting. What about IPv6 module? Based on my understanding, it should
always be loaded before we can trigger udp_bpf_check_v6_needs_rebuild().
If so, your patch is complete.
That's my understanding as well. The lazy update_proto call chain is:
sock_map_update_common
sock_map_link
sock_map_init_proto
psock->psock_update_sk_prot
udp_bpf_update_proto
udp_bpf_check_v6_needs_rebuild
If that happens we are being passed an AF_INET6 socket. Socket has been
created so IPv6 module must have been loaded.