xt_find_jump_offset(9)
okay bestie, this is xt_find_jump_offset(9), straight from the Kernel API Manual, and we're about to make jump-offset checking make sense π
β¨
πΈ NAME πΈ
xt_find_jump_offset β checks if target is a valid jump offset, no cap π―
β¨ SYNOPSIS β¨
bool xt_find_jump_offset (const unsigned int *offsets , unsigned int target , unsigned int size );
π ARGUMENTS π
offsetsβ an array holding all the valid rule start offsets of a rule blob, literally the little map of where rules can start πΊοΈβ¨targetβ the jump target we're searching for, the one getting the vibe check ππsizeβ how many entries are inoffsetβ yes, singularoffset, that's what the page says, iykyk ππ«Ά
π¦ SEE ALSO π¦
- Kernel file:
./net/netfilter/x_tables.cπ xt_check_proc_name(9)xt_check_entry_offsets(9)xt_alloc_entry_offsets(9)xt_copy_counters(9)xt_unregister_table_pre_exit(9)xt_unregister_table_exit(9)xt_hook_ops_alloc(9)xt_percpu_counter_alloc(9)
okay that's the whole page, bestie π brought to you by the footer source/version ./net/netfilter, dated October 2026, and starring xt_find_jump_offset(9) β love u, bye π«Άπ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms