iptfs_input_ordered(9)

Okay bestie, buckle up: this is iptfs_input_ordered(9) from the Kernel API Manual, and it’s giving “small function, very important job” energy 💅✨

💖 NAME 💖

iptfs_input_ordered — handle next in order IPTFS payload. That’s the whole name vibe, no cap.

✨ SYNOPSIS ✨

void iptfs_input_ordered (struct xfrm_state *x , struct sk_buff *skb );

🫶 ARGUMENTS 🫶

• x — the xfrm state. Yes, literally an xfrm state 🦋
• skb — the current packet. The packet in question, the main-character skb 👑

🌸 DESCRIPTION 🌸

So what does it actually do? It processes the IPTFS payload in skb and consumes skb afterwards. That’s the description, bestie — it handles the payload, then eats the skb. No crumbs left behind 💀✨

🦋 SEE ALSO 🦋

Related pages and the kernel file are all right here — collect them like little lore drops 🎀

• Kernel file ./net/xfrm/xfrm_iptfs.c
• IPTFS_DEFAULT_DROP_TIME_USECS(9)
• IPTFS_DEFAULT_REORDER_WINDOW(9)
• IPTFS_DEFAULT_INIT_DELAY_USECS(9)
• IPTFS_DEFAULT_MAX_QUEUE_SIZE(9)
• struct xfrm_iptfs_config(9)
• struct xfrm_iptfs_data(9)
• iptfs_alloc_skb(9)
• iptfs_skb_head_to_frag(9)
• struct iptfs_skb_frag_walk(9)
• iptfs_skb_prepare_frag_walk(9)
• iptfs_skb_can_add_frags(9)
• iptfs_skb_add_frags(9)
• iptfs_pskb_add_frags(9)
• iptfs_pskb_extract_seq(9)
• iptfs_input_save_runt(9)
• __iptfs_iphlen(9)
• __iptfs_iplen(9)
• iptfs_complete_inner_skb(9)
• iptfs_reassem_abort(9)
• iptfs_reassem_done(9)
• iptfs_reassem_cont(9)
• iptfs_drop_timer(9)
• iptfs_input(9)
• iptfs_enqueue(9)
• iptfs_copy_create_frag(9)
• iptfs_copy_create_frags(9)
• iptfs_first_skb(9)
• iptfs_encap_add_ipv4(9)
• iptfs_encap_add_ipv6(9)
• iptfs_prepare_output(9)
• __iptfs_get_inner_mtu(9)
• iptfs_get_inner_mtu(9)
• iptfs_user_init(9)

And that’s the page, bestie — source/version: ./net/xfrm, date: October 2026 🌈💖✨