nft_data_hold(9)

🎀 nft_data_hold(9) — Kernel API Manual 🎀

🌸 NAME 🌸

nft_data_hold — hold a nft_data item

✨ SYNOPSIS ✨

       void nft_data_hold (const struct nft_data *data , enum nft_data_types
       type );

🎀 ARGUMENTS 🎀

• data — a struct nft_data to release. Yes, the original literally says “to release” in a function called hold — we are just reporting the lore, bestie 😭💅
• type — type of data (enum nft_data_types, per the synopsis ✨)

💅 DESCRIPTION 💅

Okay so this function holds a nft_data item. For NFT_DATA_VALUE types, the hold can be silently discarded — silently, bestie, like it never even said anything 💀.

For NFT_DATA_VERDICT, it bumps the reference to chains in case of NFT_JUMP and NFT_GOTO verdicts. Those are the verdicts named in the manual, periodt 👑.

This function must be called on active data objects from the second phase of the commit protocol. That must is doing main character energy — do not ignore it, fr fr 🫶.

🦋 SEE ALSO 🦋

Kernel file ./net/netfilter/nf_tables_api.c — go peek if you want the whole vibe 😌

Also peep: nft_register_expr(9), nft_unregister_expr(9), nft_register_obj(9), nft_unregister_obj(9), nft_parse_u32_check(9), nft_dump_register(9), nft_data_init(9), nft_data_release(9)

Signed off from ./net/netfilter 💖 stamped October 2026 💖 page nft_data_hold(9) — bye bestie, slay responsibly 💜