[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87y2aar6yi.fsf@cloudflare.com>
Date: Tue, 13 Jul 2021 09:47:17 +0200
From: Jakub Sitnicki <jakub@...udflare.com>
To: John Fastabend <john.fastabend@...il.com>
Cc: ast@...nel.org, daniel@...earbox.net, andriin@...com,
xiyou.wangcong@...il.com, bpf@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH bpf v4 0/2] bpf, sockmap: fix potential memory leak
On Mon, Jul 12, 2021 at 09:55 PM CEST, John Fastabend wrote:
> 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(-)
For the series:
Acked-by: Jakub Sitnicki <jakub@...udflare.com>
Powered by blists - more mailing lists