From: Jakub Kicinski <kuba@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Willem de Bruijn <willemb@google.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next] udp: remove busylock and add per NUMA queues
Date: Fri, 19 Sep 2025 13:16:07 -0700 [thread overview]
Message-ID: <20250919131607.66e74a10@kernel.org> (raw)
In-Reply-To: <20250919164308.2455564-1-edumazet@google.com>
On Fri, 19 Sep 2025 16:43:08 +0000 Eric Dumazet wrote:
> @@ -2906,6 +2912,7 @@ void udp_destroy_sock(struct sock *sk)
> udp_tunnel_cleanup_gro(sk);
> }
> }
> + kfree(up->udp_prod_queue);
> }
CI lit up with memory leaks. Looks like IPv6 destroy needs a copy of
the kfree()?
next prev parent reply other threads:[~2025-09-19 20:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 16:43 [PATCH net-next] udp: remove busylock and add per NUMA queues Eric Dumazet
2025-09-19 20:16 ` Jakub Kicinski [this message]
2025-09-19 20:22 ` Eric Dumazet
2025-09-20 1:18 ` Kuniyuki Iwashima
2025-09-20 6:52 ` Eric Dumazet
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=20250919131607.66e74a10@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuniyu@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox