iptfs_copy_create_frag(9)

✨ iptfs_copy_create_frag(9) ✨

okay so bestie, welcome to the Kernel API Manual — this page is literally all about iptfs_copy_create_frag(9), and we’re gonna get you comfy with it 💖.

💖 NAME 💖

iptfs_copy_create_frag — create an inner fragment skb.

🌸 SYNOPSIS 🌸

struct sk_buff * iptfs_copy_create_frag (struct skb_seq_state *st , u32 offset , u32 copy_len );

🦋 ARGUMENTS 🦋

• st — the source packet data.
• offset — offset in st of the new fragment data.
• copy_len — the amount of data to copy from st.

✨ DESCRIPTION ✨

So what’s the vibe? It creates a new skb holding a single IPTFS inner packet fragment. That’s the whole main character move 💅.

⚠️ important heads-up, bestie: copy_len must not be greater than the max fragment size. Like, do not push that limit — it’s a hard no, periodt.

🎀 RETURN 🎀

It returns the new fragment skb or an ERR_PTR — those are the two outcomes, no cap 🫶.

🔥 SEE ALSO 🔥

okay these are the kernel-file friends and the whole iptfs crew, all together:

• 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_input_ordered(9)
• iptfs_drop_timer(9)
• iptfs_input(9)
• iptfs_enqueue(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)

mwah 💋 — this page is from ./net/xfrm, dated October 2026.