From 586e1ba238eeb5aae7659a9b2ea2843d070de65e Mon Sep 17 00:00:00 2001 From: Vyron Vasileiadis Date: Fri, 28 Aug 2026 02:16:51 +0300 Subject: [PATCH] docs(cuda.core): correct the 1.1.1 program cache permissions note The note described the first draft of #2399. Review narrowed the change to the tmp/ staging directory, so only tmp/ is created 0o700 and the post-mkdir chmod was dropped. The cache root and entries/ inherit the umask and a pre-existing directory is left as-is, so nothing is re-asserted on each use. Entry files are 0o600 via mkstemp and an atomic replace, so the note's read-protection claim is kept. Closes #2717 --- cuda_core/docs/source/release/1.1.1-notes.rst | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/cuda_core/docs/source/release/1.1.1-notes.rst b/cuda_core/docs/source/release/1.1.1-notes.rst index 66d74e3540b..09ea7a0b254 100644 --- a/cuda_core/docs/source/release/1.1.1-notes.rst +++ b/cuda_core/docs/source/release/1.1.1-notes.rst @@ -41,10 +41,12 @@ Fixes and enhancements internal driver thread. (`#2371 `__) -- The on-disk program cache directory is now created with owner-only - permissions (``0o700``) on POSIX systems, and those permissions are - re-asserted on each use. This prevents other local users from reading or - injecting cached device code regardless of the process ``umask``. +- Program cache entry files are now written with owner-only permissions + (``0o600``) on POSIX systems, and the ``tmp/`` staging directory is created + ``0o700``, so other local users cannot read cached device code regardless of + the process ``umask``. The cache root and ``entries/`` inherit the umask and + a pre-existing cache directory is used as-is, so a deliberately shared cache + keeps working. (`#2399 `__) - DLPack: a ``NULL`` deleter in a ``DLManagedTensorVersioned`` capsule is now