iscsi_tcp_recv_skb(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… iscsi_tcp_recv_skb(9) β€” the "process skb" one, from the Kernel API Manual

okay so bestie, picture this: you're deep in the kernel, there's a socket buffer staring at you, and somebody has to actually do something with it. That somebody is iscsi_tcp_recv_skb, and honestly? She ate. Let's get into it 🫢


✨ SYNOPSIS ✨

int iscsi_tcp_recv_skb (struct iscsi_conn *conn , struct sk_buff *skb ,
       unsigned int offset , bool offloaded , int *status );

that's the whole vibe check right there β€” int in, bytes out, no cap πŸ’–


πŸŽ€ ARGUMENTS πŸŽ€

  • conn β€” the iscsi connection, aka the main character of this whole situation 🌸
  • skb β€” the network buffer holding the header and/or data segment. literally the package we're opening πŸ“¦
  • offset β€” offset in skb, because sometimes you don't start at the beginning, bestie πŸ’…
  • offloaded β€” a bool that tells you whether the transfer was offloaded or not. just a lil yes/no slay ✨
  • status β€” the iscsi TCP status result, which is where the answer gets written back. iconic behavior πŸŽ€

πŸ¦‹ DESCRIPTION πŸ¦‹

so what does she actually do? She'll return the status of the transfer in status β€” and then she'll also return the number of bytes copied. Two things at once, multitasking queen πŸ‘‘βœ¨

like, that's it, that's the job. She processes the skb, drops the status where you asked her to, and tells you how many bytes she got through. no drama, no notes πŸ”₯

ngl the docs are short here β€” if you want the actual mechanics, the SEE ALSO squad below is where the story continues 🫢

🌈 SEE ALSO 🌈

all the besties she hangs out with in the Kernel file ./drivers/scsi/libiscsi_tcp.c:

the whole friend group fr fr πŸ’œ


aw and one last thing bestie β€” this page lives over in ./drivers/scsi, and it's stamped October 2026 πŸŽ€ mwah, go read some more kernel docs, ily πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from