Skip to content

Containers need to use hsa devices for ROCM #384

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 3, 2025
Merged

Conversation

rhatdan
Copy link
Member

@rhatdan rhatdan commented Jul 2, 2025

Summary by Sourcery

Enhancements:

  • Allow containers to access HSA device nodes required by ROCm

Copy link

sourcery-ai bot commented Jul 2, 2025

Reviewer's Guide

This PR extends the SELinux container policy to allow containerized workloads to access AMD ROCm HSA devices by defining a new device type for HSA and granting the container domains the needed permissions.

File-Level Changes

Change Details Files
Define and label a new HSA device type
  • Introduce hsa_device_t in the SELinux policy
  • Add file context mapping for /dev/kfd to hsa_device_t
container.te
file_contexts
Grant container domains access to HSA devices
  • Allow container_t open/read/write/ ioctl on hsa_device_t
  • Grant the container runtime domain the same permissions
container.te

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@openshift-ci openshift-ci bot added the approved label Jul 2, 2025
Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @rhatdan - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @rhatdan, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the SELinux policy for containers to grant them the necessary permissions to access HSA (Heterogeneous System Architecture) devices. This change is specifically aimed at enabling and improving support for ROCm (Radeon Open Compute platform) within containerized environments, ensuring applications can properly interact with GPU hardware.

Highlights

  • SELinux Policy Version Bump: The container SELinux policy module version has been incremented from 2.238.0 to 2.239.0.
  • ROCm/HSA Device Access for Containers: A new optional_policy rule has been added to allow container_domain read and write permissions (rw_chr_file_perms) to character files of type hsa_device_t. This change is essential for enabling ROCm (Radeon Open Compute platform) functionality within containers by granting them access to Heterogeneous System Architecture (HSA) devices.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request adds SELinux rules to allow containers to access HSA devices for ROCm. For better security and consistency, the new rule should be controlled by a tunable boolean. I've suggested this improvement.

Comment on lines +710 to +716
optional_policy(`
require {
type hsa_device_t;
}

allow container_domain hsa_device_t:chr_file rw_chr_file_perms;
')

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

For consistency with other device access rules in this policy and for better security, this new permission should be controlled by a tunable boolean. This allows administrators to explicitly enable HSA device access when needed, instead of granting it by default on systems with ROCm support. Please wrap this policy in a tunable_policy block and add a corresponding gen_tunable definition1.

tunable_policy(`container_use_hsa_devices',`
	optional_policy(`
		require {
			type hsa_device_t;
		}

		allow container_domain hsa_device_t:chr_file rw_chr_file_perms;
	')
`)

Style Guide References

Footnotes

  1. Use tunable policies for device access control to allow administrators to explicitly enable features. (link)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No I don't want to wrap this in a boolean, it is needed in general for ROCM accelerators, so I want it on by default.

@rhatdan rhatdan added the lgtm label Jul 2, 2025
@rhatdan
Copy link
Member Author

rhatdan commented Jul 3, 2025

@lsm5 Can't get this merged because the tests are blocked?

@lsm5
Copy link
Member

lsm5 commented Jul 3, 2025

@lsm5 Can't get this merged because the tests are blocked?

Let me check on this and get back in a bit.

Copy link
Member

@lsm5 lsm5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Copy link

openshift-ci bot commented Jul 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lsm5, rhatdan, sourcery-ai[bot]

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@lsm5 lsm5 merged commit 9693071 into containers:main Jul 3, 2025
2 of 24 checks passed
@lsm5
Copy link
Member

lsm5 commented Jul 3, 2025

Bypassed rules and merged. Packit jobs are blocked on https://status.packit.dev/issues/2025-06-30-fedora-infra-migration/

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.

2 participants