You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 974a7ad
Browse filesBrowse the repository at this point in the historyBrowse files
cuda.core: scope the child-graph registry to the parent GraphBox
The process-wide graph registry mapped a raw CUgraph to its canonical
GraphHandle. Every handle of a hierarchy aliases the hierarchy's single
control block, so a lockable registry entry proved only that the hierarchy
was alive, not that the child graph was. CUDA destroys a child graph inside
cuGraphDestroyNode, cuGraphNodeSetParams, or capture invalidation, and the
box is retired only after the driver call returns. In that window the map
could hand one hierarchy's recycled address to another.
The only reader, create_child_graph_handle, always knows the parent, and
roots are never looked up. Each GraphBox now holds the registry of its
direct child graphs, next to its node registry. A recycled address can only
collide inside one hierarchy, where mutations are externally synchronized
and every retire precedes the matching registration. The conditional
unregister_handle overload, the bulk register_handles, the static registry,
and the hierarchy deleter's unregister loop are gone. The same-parent
registry test modeled two live generations at one address under one parent,
which the synchronization contract excludes, and is removed.
Written by Codex (gpt-6.1-sol); reviewed by Claude.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
0 commit comments