nft_pipapo_flush(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so bestie, this is the page for nft_pipapo_flush(9) from the Kernel API Manual β€” folding that manual name in right here near the top, cute and all. The whole name-and-purpose vibe is: nft_pipapo_flush β€” make element inactive. πŸ’…βœ¨

✨ SYNOPSIS ✨

Here's the signature, exactly as the page has it:

void nft_pipapo_flush (const struct net *net , const struct nft_set *set
, struct nft_elem_priv *elem_priv );

πŸŽ€ ARGUMENTS πŸŽ€

  • net β€” Network namespace.
  • set β€” nftables API set representation.
  • elem_priv β€” nftables API element representation containing key data.

🌸 DESCRIPTION 🌸

This is functionally the same as nft_pipapo_deactivate, with a slightly different interface, and the way that it's also called once for each element in a set being flushed means we can't implement, strictly speaking, a flush operation β€” which would otherwise be as simple as allocating an empty copy of the matching data. no cap. πŸ’–

⚠️ Note that we could in theory do that, mark the set as flushed, and ignore subsequent calls, but we would leak all the elements after the first one, because they wouldn't then be freed as result of API calls. πŸ˜­πŸ’€

πŸ”₯ RETURN πŸ”₯

Return vibe check: true if element was found and deactivated. slay. ✨

πŸ¦‹ SEE ALSO πŸ¦‹


byeee bestie, this page came from ./net/netfilter, October 2026 β€” mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from