[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9d9fa546-ca92-4ea4-90c5-128cacb293e3@openvpn.net>
Date: Mon, 2 Dec 2024 04:53:46 +0100
From: Antonio Quartulli <antonio@...nvpn.net>
To: Sabrina Dubroca <sd@...asysnail.net>,
Sergey Ryazanov <ryazanov.s.a@...il.com>
Cc: Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, Donald Hunter <donald.hunter@...il.com>,
Andrew Lunn <andrew@...n.ch>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
Shuah Khan <shuah@...nel.org>
Subject: Re: [PATCH net-next v11 09/23] ovpn: implement basic RX path (UDP)
On 29/11/2024 17:10, Sabrina Dubroca wrote:
> Related to that topic, I'm not sure what's keeping a reference on the
> peer to guarantee it doesn't get freed before we're done with
> peer->tcp.tx_work at the end of ovpn_tcp_socket_detach. Maybe all this
> tcp stuff should move from the peer to ovpn_socket?
Actually, with the new approach of "keeping the reference to the peer
until the socket is gone" we can simply ensure the reference is dropped
at the very end of the detach, after cancel_work_sync() is done.
This way we know for sure that every activity is done and can release
the peer.
Regards,
--
Antonio Quartulli
OpenVPN Inc.
Powered by blists - more mailing lists