drm_vma_node_allow_once(9)
π drm_vma_node_allow_once(9) π
okay so bestie, this is one of those kernel API manual pages β it lives in the Kernel API Manual, and it's about drm_vma_node_allow_once, which is literally "Add open-file to list of allowed users." One open-file, one shot, no take-backs. π
β¨ SYNOPSIS β¨
int drm_vma_node_allow_once (struct drm_vma_offset_node *node , struct
drm_file *tag );
like. that's the whole signature. it returns an int, it takes a node and a tag, and yes the formatting is doing that awkward line-break thing. we don't judge. π¦
πΈ ARGUMENTS πΈ
nodeβ Node to modify. this is the vma offset node you're messing with, bestie.tagβ Tag of file to remove. (yes, it says "remove" in the argument blurb even though the function adds β that's what the page literally says, so we're passing that along verbatim, no cap π)
π DESCRIPTION π
So what it does: it adds tag to the list of allowed open-files for this node. That's the whole vibe. β¨
The list of allowed-users is preserved across drm_vma_offset_add and drm_vma_offset_remove calls. like, those calls do not clear it out, the list stays. You may even call it if the node is currently not added to any offset-manager β icon status honestly. π
π¨ important caveat, please read this one: this is not ref-counted, unlikedrm_vma_node_allow. sodrm_vma_node_revokeshould only be called once after this. once! not twice! not in a loop! the way that ref-counting does not exist here is genuinely something to remember. π
Also, this is locked against concurrent access internally β the kernel handles the locking for you, so you don't have to do the whole mutex dance yourself. slay. π«Ά
β RETURN β
0on success π- negative error code on internal failure (out-of-mem) π
π SEE ALSO π
go read these next, they're all in the same universe:
- Kernel file
./drivers/gpu/drm/drm_vma_manager.c vma offset manager(9)drm_vma_offset_manager_init(9)drm_vma_offset_manager_destroy(9)drm_vma_offset_lookup_locked(9)drm_vma_offset_add(9)drm_vma_offset_remove(9)drm_vma_node_allow(9)drm_vma_node_revoke(9)drm_vma_node_is_allowed(9)
and that's the page, bestie π β sourced from ./drivers/gpu/drm, dated October 2026, part of the Kernel API Manual, filed under drm_vma_node_allow_once(9). go forth and call it exactly once, mwah π§π
π¦ 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