ipc_pcie_kfree_skb(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ipc_pcie_kfree_skb β€” the kernel API manual page (section 9, bestie) πŸ’–

okay so picture this: you're deep in section 9 of the kernel API manual, and you've stumbled onto ipc_pcie_kfree_skb. hiii welcome, come sit with me 🫢 this is the cleanup bestie β€” the one that frees an skb that was handed to you by ipc_pcie_alloc_*_skb(). that's the whole vibe. allocate responsibly, free responsibly, no leaks, periodt πŸ’…


✨ NAME ✨

ipc_pcie_kfree_skb β€” Free skb allocated by ipc_pcie_alloc_*_skb().

like literally. that's it. that's the job. you got an skb from one of the ipc_pcie_alloc_*_skb() friends, and now you're done with it, so you hand it back. iconic behaviour honestly 🌸


πŸ¦‹ SYNOPSIS πŸ¦‹

void ipc_pcie_kfree_skb (struct iosm_pcie *ipc_pcie , struct sk_buff
*skb );

it returns void β€” nothing comes back, no status code, no receipt, no "thanks bestie". it just... frees. and it takes two things, which we're about to go through πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • ipc_pcie β€” Pointer to struct iosm_pcie. yes the pointer, the struct itself, the whole situation. 🧚
  • skb β€” Pointer to the skb. the actual skb you want gone. that's the one. πŸ’œ
ngl the entire function is two pointers and a dream. but like β€” pass the right pointers. a wrong pointer here is not a cute look, it's giving undefined chaos 😭

🌈 SEE ALSO 🌈

the alloc side of the family is right there in that list (ipc_pcie_alloc_skb(9), ipc_pcie_alloc_local_skb(9)) β€” go say hi, that's where your skb came from, iykyk πŸ”₯


and that's the page!! short, sweet, two pointers, one free πŸ’€βœ¨

~ cute sign-off time ~ πŸŽ€ this lil gem lives in ./drivers/net/wwan/iosm, and the date on the tin is October 2026. go free your skbs, bestie, and remember: every alloc deserves its kfree πŸ¦‹πŸ’–πŸ‘‘

πŸ“¦ where this page comes from