From: patchwork-bot+netdevbpf@kernel.org
To: Antonio Quartulli <antonio@openvpn.net>
Cc: netdev@vger.kernel.org, sd@queasysnail.net, kuba@kernel.org,
pabeni@redhat.com, davem@davemloft.net, edumazet@google.com,
andrew+netdev@lunn.ch, ralf@mandelbit.com, a0yami@mailbox.org,
horms@kernel.org
Subject: Re: [PATCH net 1/6] ovpn: avoid putting unrelated P2P peer on socket release
Date: Thu, 23 Jul 2026 17:10:16 +0000 [thread overview]
Message-ID: <178482661640.2789426.16690142104859181544.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260720144131.3657121-2-antonio@openvpn.net>
Hello:
This series was applied to netdev/net.git (main)
by Antonio Quartulli <antonio@openvpn.net>:
On Mon, 20 Jul 2026 16:41:26 +0200 you wrote:
> From: Qing Ming <a0yami@mailbox.org>
>
> ovpn_peer_release_p2p() is called when an OVPN UDP socket is being
> destroyed. It checks the currently published P2P peer and releases it only
> if that peer still uses the socket being destroyed.
>
> A peer replacement can publish a new peer before the old UDP socket is
> destroyed. When the old socket destruction path runs afterwards,
> ovpn_peer_release_p2p() observes the new peer through ovpn->peer. Since the
> new peer uses a different socket, the function takes the socket mismatch
> branch.
>
> [...]
Here is the summary with links:
- [net,1/6] ovpn: avoid putting unrelated P2P peer on socket release
https://git.kernel.org/netdev/net/c/b52c5103f64e
- [net,2/6] ovpn: fix peer refcount leak in TCP error paths
https://git.kernel.org/netdev/net/c/63bbe18fc030
- [net,3/6] ovpn: hold peer before scheduling keepalive work
https://git.kernel.org/netdev/net/c/a4710ae2e7e3
- [net,4/6] selftests/net: ovpn: fix getaddrinfo memory leak in ovpn_parse_remote()
https://git.kernel.org/netdev/net/c/0bd9cfebc1c9
- [net,5/6] ovpn: fix use after free in unlock_ovpn()
https://git.kernel.org/netdev/net/c/e1ad6fe5db71
- [net,6/6] ovpn: use monotonic clock for peer keepalive timeouts
https://git.kernel.org/netdev/net/c/f7e6287ccd3a
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:[~2026-07-23 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 14:41 [PATCH net 0/6] pull request: fixes for ovpn 2026-07-20 Antonio Quartulli
2026-07-20 14:41 ` [PATCH net 1/6] ovpn: avoid putting unrelated P2P peer on socket release Antonio Quartulli
2026-07-23 17:10 ` patchwork-bot+netdevbpf [this message]
2026-07-20 14:41 ` [PATCH net 2/6] ovpn: fix peer refcount leak in TCP error paths Antonio Quartulli
2026-07-20 14:41 ` [PATCH net 3/6] ovpn: hold peer before scheduling keepalive work Antonio Quartulli
2026-07-20 14:41 ` [PATCH net 4/6] selftests/net: ovpn: fix getaddrinfo memory leak in ovpn_parse_remote() Antonio Quartulli
2026-07-20 14:41 ` [PATCH net 5/6] ovpn: fix use after free in unlock_ovpn() Antonio Quartulli
2026-07-20 14:41 ` [PATCH net 6/6] ovpn: use monotonic clock for peer keepalive timeouts Antonio Quartulli
-- strict thread matches above, loose matches on Subject: below --
2026-06-08 15:07 [PATCH net 0/6] pull request: fixes for ovpn 2026-06-08 Antonio Quartulli
2026-06-08 15:07 ` [PATCH net 1/6] ovpn: avoid putting unrelated P2P peer on socket release Antonio Quartulli
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=178482661640.2789426.16690142104859181544.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=a0yami@mailbox.org \
--cc=andrew+netdev@lunn.ch \
--cc=antonio@openvpn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ralf@mandelbit.com \
--cc=sd@queasysnail.net \
/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.