iscsi_tcp_hdr_recv_done(9)

💖 iscsi_tcp_hdr_recv_done(9) 💖

okay bestie, this page is from the Kernel API Manual, and we're talking about iscsi_tcp_hdr_recv_done(9). It's giving kernel callback main character energy, and yes, we're gonna get through every single detail together. 🫶

✨ NAME ✨

iscsi_tcp_hdr_recv_done — process PDU header

🎀 SYNOPSIS 🎀

int iscsi_tcp_hdr_recv_done (struct iscsi_tcp_conn *tcp_conn , struct
       iscsi_segment *segment );

🦋 ARGUMENTS 🦋

• tcp_conn — the iSCSI TCP connection, aka the connection bestie in question. 💜
• segment — the buffer segment being processed, aka the chunk we're looking at. 🌸

🌈 DESCRIPTION 🌈

So this is the callback invoked when the PDU header has been received. That's the whole vibe. If the header is followed by additional header segments, we go back for more data. Literally: more header? go back, grab more data, repeat. No cap. ✨

ngl this is a very "callback does its little job and loops for more" situation. 💅

⭐ SEE ALSO ⭐

The kernel file is ./drivers/scsi/libiscsi_tcp.c, and the related crew is:

• iscsi_tcp_segment_init_sg(9)
• iscsi_tcp_segment_map(9)
• iscsi_tcp_segment_done(9)
• iscsi_tcp_segment_recv(9)
• iscsi_tcp_hdr_recv_prep(9)
• iscsi_tcp_cleanup_task(9)
• iscsi_tcp_data_in(9)
• iscsi_tcp_r2t_rsp(9)
• iscsi_tcp_hdr_dissect(9)
• iscsi_tcp_recv_segment_is_hdr(9)
• iscsi_tcp_recv_skb(9)
• iscsi_tcp_task_init(9)
• iscsi_tcp_task_xmit(9)

and that's the page, bestie! 🎀 sign-off time: the footer energy is source/version ./drivers/scsi, date October 2026, and title iscsi_tcp_hdr_recv_done(9). slay, go touch some kernel code, periodt. 💅✨