From: patchwork-bot+netdevbpf@kernel.org
To: Joas Antonio dos Santos <joasantonio108@gmail.com>
Cc: pablo@netfilter.org, laforge@gnumonks.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, osmocom-net-gprs@lists.osmocom.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net] gtp: free the skb after handling an echo response
Date: Thu, 12 Nov 2026 18:00:05 +0000 [thread overview]
Message-ID: <179450640576.567589.2698592522112399495.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261110-gtp-echo-rsp-leak-v1-1-192c032f3dfa@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 10 Nov 2026 09:03:26 +0000 you wrote:
> From: Joas Antonio dos Santos <joasantonio108@gmail.com>
>
> gtp0_handle_echo_resp() and gtp1u_handle_echo_resp() return the result
> of genlmsg_multicast_netns() to gtp_encap_recv(). When the netlink
> notification is delivered that result is 0, and gtp_encap_recv() treats
> 0 as "the skb has been consumed":
>
> [...]
Here is the summary with links:
- [net] gtp: free the skb after handling an echo response
https://git.kernel.org/netdev/net/c/f17b293d155f
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:[~2026-11-12 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 9:03 [PATCH net] gtp: free the skb after handling an echo response Joas Antonio dos Santos
2026-11-10 9:03 ` Joas Antonio dos Santos via B4 Relay
2026-11-10 13:08 ` Markus Elfring
2026-11-11 2:03 ` Joas Antonio
2026-11-12 17:53 ` Jakub Kicinski
2026-11-12 18:00 ` 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=179450640576.567589.2698592522112399495.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=joasantonio108@gmail.com \
--cc=kuba@kernel.org \
--cc=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=osmocom-net-gprs@lists.osmocom.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=stable@vger.kernel.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.