[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210712195546.423990-1-john.fastabend@gmail.com>
Date: Mon, 12 Jul 2021 12:55:44 -0700
From: John Fastabend <john.fastabend@...il.com>
To: ast@...nel.org, jakub@...udflare.com, daniel@...earbox.net,
andriin@...com, xiyou.wangcong@...il.com
Cc: bpf@...r.kernel.org, netdev@...r.kernel.org,
john.fastabend@...il.com
Subject: [PATCH bpf v4 0/2] bpf, sockmap: fix potential memory leak
While investigating a memleak in sockmap I found these two issues. Patch
1 found doing code review, I wasn't able to get KASAN to trigger a
memleak here, but should be necessary. Patch 2 fixes proc stats so when
we use sockstats for debugging we get correct values.
The fix for observered memleak will come after these, but requires some
more discussion and potentially patch revert so I'll try to get the set
here going now.
v4: fix both users of sk_psock_skb_ingress_enqueue and then fix the
inuse idx by moving init hook later after tcp/udp init calls.
v3: move kfree into same function as kalloc
John Fastabend (2):
bpf, sockmap: fix potential memory leak on unlikely error case
bpf, sockmap: sk_prot needs inuse_idx set for proc stats
net/core/skmsg.c | 16 +++++++++++-----
net/core/sock_map.c | 11 ++++++++++-
2 files changed, 21 insertions(+), 6 deletions(-)
--
2.25.1
Powered by blists - more mailing lists