ovs_vport_ge...call_portids(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ovs_vport_ge...call_portids(9) — the Kernel API Manual era ✨

okay bestie, buckle up, we're diving into the Kernel API Manual 💖 and honestly? this one's a little nugget of a function and it's serving exactly what it needs to serve.

🌸 NAME 🌸

ovs_vport_get_upcall_portids — literally just get the upcall_portids of @vport. that's the whole vibe. that's the assignment. 🎀

✨ SYNOPSIS ✨

int ovs_vport_get_upcall_portids (const struct vport *vport , struct sk_buff *skb );

like yes, that is the signature, no cap, copied exactly, don't come for me 🫶

🦋 ARGUMENTS 🦋

  • vport — the vport you're pulling the portids out of, bestie. your source. your main character struct. 👑
  • skb — the sk_buff where the portids are gonna get appended. think of it as the cute little bag you're packing the data into 🎀

💜 DESCRIPTION 💜

so the way this works 💅 — it retrieves the configuration of the given vport, and appends the OVS_VPORT_ATTR_UPCALL_PID attribute to skb, which is the array of upcall portids. iconic. no notes.

it returns 0 if successful ✨ — but if skb doesn't have enough room? it's giving -EMSGSIZE, iykyk. 😭 and if an error occurs, skb is left unmodified — untouched, unbothered, living its life, we do not touch the skb on a bad day, periodt.

🚨 okay so important caveat bestie: this must be called with ovs_mutex or rcu_read_lock. like you literally cannot skip this. this is the vibe check and you WILL pass it. 🔥

🌈 SEE ALSO 🌈

all the siblings, all the lore, all in the kernel file ./net/openvswitch/vport.c 🧚:

fr fr, go read them, they're all eating 🔥

and that's the tea 🍓 — this little page lives in ./net/openvswitch, dated October 2026, and its whole header/footer situation is ovs_vport_ge...call_portids(9) (yes the truncation is real, we love an ellipsis moment 💀). mwah, study well, slay the kernel 💅💖✨

📦 where this page comes from