unlink_anon_vmas(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

unlink_anon_vmas β€” remove all links between a VMA and anon_vma's, freeing anon_vma_chain objects.


🌈 SYNOPSIS 🌈

void unlink_anon_vmas (struct vm_area_struct *vma );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • vma β€” the VMA whose links to anon_vma objects is to be severed. yes bestie, this is the one getting its links cut πŸ’…

✨ DESCRIPTION ✨

okay so here's the tea: as part of the process, the anon_vma_chain's are freed, anon_vma->num_children,num_active_vmas is updated as required, and if the relevant anon_vma references no further VMAs, its reference count is decremented. periodt. 🫢


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./mm/rmap.c has the whole squad: __anon_vma_prepare(9), anon_vma_clone(9), page_address_in_vma(9), folio_referenced(9), mapping_wrprotect_range(9), pfn_mkclean_range(9), folio_move_anon_rmap(9), __folio_set_anon(9), __page_check_anon_rmap(9), folio_add_anon_rmap_ptes(9), folio_add_anon_rmap_pmd(9), folio_add_new_anon_rmap(9), folio_add_file_rmap_ptes(9), folio_add_file_rmap_pmd(9), folio_add_file_rmap_pud(9), folio_remove_rmap_ptes(9), folio_remove_rmap_pmd(9), folio_remove_rmap_pud(9), try_to_unmap(9), try_to_migrate(9), make_device_exclusive(9), and __rmap_walk_file(9). iykyk 🌟


byeee bestie πŸ’… this page is from ./mm, dated October 2026, and it's literally unlink_anon_vmas(9) signing off 🫢✨

πŸ“¦ where this page comes from