From: patchwork-bot+netdevbpf@kernel.org
To: wangyufen <wangyufen@huawei.com>
Cc: john.fastabend@gmail.com, daniel@iogearbox.net,
jakub@cloudflare.com, lmb@cloudflare.com, davem@davemloft.net,
bpf@vger.kernel.org, edumazet@google.com,
yoshfuji@linux-ipv6.org, dsahern@kernel.org, kuba@kernel.org,
ast@kernel.org, andrii@kernel.org, kafai@fb.com,
songliubraving@fb.com, yhs@fb.com, kpsingh@kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 0/4] bpf, sockmap: Fix memleaks and issues of mem charge/uncharge
Date: Tue, 15 Mar 2022 15:50:11 +0000 [thread overview]
Message-ID: <164735941157.4881.17090692944812757596.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220304081145.2037182-1-wangyufen@huawei.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Fri, 4 Mar 2022 16:11:41 +0800 you wrote:
> This patchset fixes memleaks and incorrect charge/uncharge memory, these
> issues cause the following info:
>
> WARNING: CPU: 0 PID: 9202 at net/core/stream.c:205 sk_stream_kill_queues+0xc8/0xe0
> Call Trace:
> <IRQ>
> inet_csk_destroy_sock+0x55/0x110
> tcp_rcv_state_process+0xe5f/0xe90
> ? sk_filter_trim_cap+0x10d/0x230
> ? tcp_v4_do_rcv+0x161/0x250
> tcp_v4_do_rcv+0x161/0x250
> tcp_v4_rcv+0xc3a/0xce0
> ip_protocol_deliver_rcu+0x3d/0x230
> ip_local_deliver_finish+0x54/0x60
> ip_local_deliver+0xfd/0x110
> ? ip_protocol_deliver_rcu+0x230/0x230
> ip_rcv+0xd6/0x100
> ? ip_local_deliver+0x110/0x110
> __netif_receive_skb_one_core+0x85/0xa0
> process_backlog+0xa4/0x160
> __napi_poll+0x29/0x1b0
> net_rx_action+0x287/0x300
> __do_softirq+0xff/0x2fc
> do_softirq+0x79/0x90
> </IRQ>
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/4] bpf, sockmap: Fix memleak in sk_psock_queue_msg
https://git.kernel.org/bpf/bpf-next/c/938d3480b92f
- [bpf-next,v3,2/4] bpf, sockmap: Fix memleak in tcp_bpf_sendmsg while sk msg is full
https://git.kernel.org/bpf/bpf-next/c/9c34e38c4a87
- [bpf-next,v3,3/4] bpf, sockmap: Fix more uncharged while msg has more_data
https://git.kernel.org/bpf/bpf-next/c/84472b436e76
- [bpf-next,v3,4/4] bpf, sockmap: Fix double uncharge the mem of sk_msg
https://git.kernel.org/bpf/bpf-next/c/2486ab434b2c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-03-15 15:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 8:11 [PATCH bpf-next v3 0/4] bpf, sockmap: Fix memleaks and issues of mem charge/uncharge Wang Yufen
2022-03-04 8:11 ` [PATCH bpf-next v3 1/4] bpf, sockmap: Fix memleak in sk_psock_queue_msg Wang Yufen
2022-03-04 8:11 ` [PATCH bpf-next v3 2/4] bpf, sockmap: Fix memleak in tcp_bpf_sendmsg while sk msg is full Wang Yufen
2022-03-11 21:55 ` John Fastabend
2022-03-04 8:11 ` [PATCH bpf-next v3 3/4] bpf, sockmap: Fix more uncharged while msg has more_data Wang Yufen
2022-03-04 8:11 ` [PATCH bpf-next v3 4/4] bpf, sockmap: Fix double uncharge the mem of sk_msg Wang Yufen
2022-03-11 21:51 ` John Fastabend
2022-03-15 15:50 ` patchwork-bot+netdevbpf [this message]
2022-10-27 21:10 ` [PATCH bpf-next v3 0/4] bpf, sockmap: Fix memleaks and issues of mem charge/uncharge Jakub Sitnicki
2022-10-28 1:41 ` wangyufen
2022-10-28 5:20 ` wangyufen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=164735941157.4881.17090692944812757596.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=lmb@cloudflare.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=wangyufen@huawei.com \
--cc=yhs@fb.com \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.