From: patchwork-bot+netdevbpf@kernel.org
To: Christoph Paasch <cpaasch@openai.com>
Cc: edumazet@google.com, ncardwell@google.com, kuniyu@google.com,
davem@davemloft.net, dsahern@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, 0x7f454c46@gmail.com,
noureddine@arista.com, fruggeri@arista.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net] net/tcp: Fix socket memory leak in TCP-AO failure handling for IPv6
Date: Tue, 02 Sep 2025 23:10:11 +0000 [thread overview]
Message-ID: <175685461125.464015.5426802978312843780.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250830-tcpao_leak-v1-1-e5878c2c3173@openai.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 30 Aug 2025 15:55:38 -0700 you wrote:
> From: Christoph Paasch <cpaasch@openai.com>
>
> When tcp_ao_copy_all_matching() fails in tcp_v6_syn_recv_sock() it just
> exits the function. This ends up causing a memory-leak:
>
> unreferenced object 0xffff0000281a8200 (size 2496):
> comm "softirq", pid 0, jiffies 4295174684
> hex dump (first 32 bytes):
> 7f 00 00 06 7f 00 00 06 00 00 00 00 cb a8 88 13 ................
> 0a 00 03 61 00 00 00 00 00 00 00 00 00 00 00 00 ...a............
> backtrace (crc 5ebdbe15):
> kmemleak_alloc+0x44/0xe0
> kmem_cache_alloc_noprof+0x248/0x470
> sk_prot_alloc+0x48/0x120
> sk_clone_lock+0x38/0x3b0
> inet_csk_clone_lock+0x34/0x150
> tcp_create_openreq_child+0x3c/0x4a8
> tcp_v6_syn_recv_sock+0x1c0/0x620
> tcp_check_req+0x588/0x790
> tcp_v6_rcv+0x5d0/0xc18
> ip6_protocol_deliver_rcu+0x2d8/0x4c0
> ip6_input_finish+0x74/0x148
> ip6_input+0x50/0x118
> ip6_sublist_rcv+0x2fc/0x3b0
> ipv6_list_rcv+0x114/0x170
> __netif_receive_skb_list_core+0x16c/0x200
> netif_receive_skb_list_internal+0x1f0/0x2d0
>
> [...]
Here is the summary with links:
- [net] net/tcp: Fix socket memory leak in TCP-AO failure handling for IPv6
https://git.kernel.org/netdev/net/c/fa390321aba0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-09-02 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 22:55 [PATCH net] net/tcp: Fix socket memory leak in TCP-AO failure handling for IPv6 Christoph Paasch
2025-08-30 22:55 ` Christoph Paasch via B4 Relay
2025-08-30 23:55 ` Dmitry Safonov
2025-09-02 23:10 ` patchwork-bot+netdevbpf [this message]
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=175685461125.464015.5426802978312843780.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=0x7f454c46@gmail.com \
--cc=cpaasch@openai.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fruggeri@arista.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=noureddine@arista.com \
--cc=pabeni@redhat.com \
/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.