__kfence_free(9)
π __kfence_free β from the Kernel API Manual, bestie π
Okay so picture this: you've got a KFENCE heap object and it's time to let it go. This function is literally the send-off. π
β¨ NAME β¨
__kfence_free β release a KFENCE heap object back to the KFENCE pool, no cap π¦
πΈ SYNOPSIS πΈ
void __kfence_free (void *addr );
π ARGUMENTS π
addrβ the object you're freeing. The one getting released. Its moment. π
π§ DESCRIPTION π§
Requires: is_kfence_address(addr) β like, this is not optional, bestie. Check it first. π
Release a KFENCE object and mark it as freed. That's the whole vibe: object released, marked freed, done. Slay. β¨
π₯ SEE ALSO π₯
Kernel file ./include/linux/kfence.h, plus the whole friend group:
is_kfence_address(9)kfence_alloc_pool_and_metadata(9)kfence_init(9)kfence_shutdown_cache(9)kfence_alloc(9)kfence_ksize(9)kfence_object_start(9)kfence_free(9)kfence_handle_page_fault(9)__kfence_obj_info(9)
Anyways, that's the page! π«Ά It lives in ./include/linux, dated October 2026, and honestly? Iconic. Go free your objects responsibly, bestie. π
π
π¦ 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