Skip to content

[release-1.18] fix: Set device node GID in CDI specs#1635

Closed
github-actions[bot] wants to merge 1 commit intorelease-1.18from
backport-1631-to-release-1.18
Closed

[release-1.18] fix: Set device node GID in CDI specs#1635
github-actions[bot] wants to merge 1 commit intorelease-1.18from
backport-1631-to-release-1.18

Conversation

@github-actions
Copy link

@github-actions github-actions bot commented Feb 6, 2026

🤖 Automated backport of #1631 to release-1.18

⚠️ This PR has merge conflicts that need manual resolution.

Original PR: #1631
Original Author: @elezar

Cherry-picked commits (1):

  • b4db92f fix: Set device node GID in CDI specs

Next Steps:

  1. Review the conflicts in the "Files changed" tab
  2. Check out this branch locally: git fetch origin backport-1631-to-release-1.18 && git checkout backport-1631-to-release-1.18
  3. Resolve conflicts manually
  4. Push the resolution: git push --force-with-lease origin backport-1631-to-release-1.18

Instructions for resolving conflicts
git fetch origin backport-1631-to-release-1.18
git checkout backport-1631-to-release-1.18
# Resolve conflicts in your editor
git add .
git commit
git push --force-with-lease origin backport-1631-to-release-1.18

This change ensures that the GID for a device node is
set in a generated CDI specification. This is important when
a device node allows users of the non-root group to access the
device node -- especially when running in non-root containers.

Signed-off-by: Evan Lezar <elezar@nvidia.com>
(cherry picked from commit b4db92f)
@copy-pr-bot
Copy link

copy-pr-bot bot commented Feb 6, 2026

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@elezar
Copy link
Member

elezar commented Feb 6, 2026

Due to the conflict, I'm closing this untill we determine whether this is required. It would also need other commits to be bacported to properly resolve conflicts.

@elezar elezar closed this Feb 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant