bond_ipsec_dev(9)
π bond_ipsec_dev β the Kernel API Manual moment β¨
okay so bestie, this is bond_ipsec_dev(9) from the kernel API manual and honestly it's giving "tiny function, big responsibilities" π let me walk you through it.
πΈ NAME πΈ
bond_ipsec_dev β get the active device for IPsec offload, no cap π
β¨ SYNOPSIS β¨
struct net_device * bond_ipsec_dev (struct xfrm_state *xs );
like, it takes one pointer and hands you back a struct net_device *, periodt π¦
π«Ά ARGUMENTS π«Ά
xsβ pointer to the transformer state struct. that's thestruct xfrm_state *, iykyk π
π₯ CONTEXT π₯
real talk: the caller must hold rcu_read_lock. not optional, not a vibe, it's the rule π
β RETURN β
it gives you the device for IPsec offload π β or NULL if it doesn't exist. that's it, that's the whole return value π
π SEE ALSO π
- Kernel file
./drivers/net/bonding/bond_main.c bond_dev_queue_xmit(9)bond_vlan_rx_add_vid(9)bond_vlan_rx_kill_vid(9)bond_ipsec_add_sa(9)bond_ipsec_del_sa(9)bond_ipsec_offload_ok(9)bond_advance_esn_state(9)bond_xfrm_update_stats(9)bond_set_dev_addr(9)bond_choose_primary_or_current(9)bond_find_best_slave(9)bond_change_active_slave(9)bond_select_active_slave(9)bond_xmit_hash(9)bond_xmit_hash_xdp(9)bond_get_slave_by_id(9)bond_rr_gen_slave_id(9)bond_sk_hash_l34(9)
like, that's a whole friend group of bonding functions and they all live together in ./drivers/net/bonding π§π
and that's the page, bestie β sourced from ./drivers/net/bonding, dated October 2026 ποΈβ¨ mwah, go hold that rcu_read_lock and slay ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms