ovpn_peer_release_p2p(9)

okay so bestie, you're looking at ovpn_peer_release_p2p(9) from the Kernel API Manual, and it is literally giving “clean up the peer when the P2P device is getting torn down” energy ✨💅

💖 NAME 💖

ovpn_peer_release_p2p — release the peer when the P2P device is being torn down 👑🦋

✨ SYNOPSIS ✨

the signature, exactly as it is, no cap:

void ovpn_peer_release_p2p (struct ovpn_priv *ovpn , struct sock *sk ,
enum ovpn_del_peer_reason reason );

🎀 ARGUMENTS 🎀

• ovpn — the instance that's getting torn down, say bye 👋
• sk — if it's not NULL, release the peer only when it's using this specific socket 🧦
• reason — the reason for releasing the peer, no mystery vibes 💅

🦋 SEE ALSO 🦋

the related-page squad, all here, all iconic:

• Kernel file: ./drivers/net/ovpn/peer.c
• ovpn_peer_keepalive_set(9)
• ovpn_peer_keepalive_send(9)
• ovpn_peer_new(9)
• ovpn_peer_reset_sockaddr(9)
• ovpn_peer_endpoints_update(9)
• ovpn_peer_release_rcu(9)
• ovpn_peer_release(9)
• ovpn_peer_release_kref(9)
• ovpn_peer_skb_to_sockaddr(9)
• ovpn_nexthop_from_skb4(9)
• ovpn_nexthop_from_skb6(9)
• ovpn_peer_get_by_vpn_addr4(9)
• ovpn_peer_get_by_vpn_addr6(9)
• ovpn_peer_vpn_addr_conflict4(9)
• ovpn_peer_vpn_addr_conflict6(9)
• ovpn_peer_transp_match(9)
• ovpn_peer_get_by_transp_addr_p2p(9)
• ovpn_peer_get_by_transp_addr(9)
• ovpn_peer_get_by_id_p2p(9)
• ovpn_peer_get_by_id(9)
• ovpn_peer_get_by_dst(9)
• ovpn_nexthop_from_rt4(9)
• ovpn_nexthop_from_rt6(9)
• ovpn_peer_check_by_src(9)
• ovpn_peer_add_mp(9)
• ovpn_peer_add_p2p(9)
• ovpn_peer_add(9)
• ovpn_peer_del_mp(9)
• ovpn_peer_del_p2p(9)
• ovpn_peer_del(9)
• ovpn_peers_free(9)
• ovpn_peer_keepalive_work(9)

catch u later from the ./drivers/net/ovpn corner of the kernel, dated October 2026 💜🫶✨