Skip to content
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

Don't map systemcfg on Power in checkpoint mode #7351

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ymanton
Copy link
Contributor

@ymanton ymanton commented May 28, 2024

On Power omrtime_current_time_millis and omrtime_hires_clock can use the timebase register to very quickly get the current time. This requires mmapping the special /proc/ppc64/systemcfg file.

Some security modules (e.g. SELinux) prevent systemcfg from being mapped by user processes. If we take a checkpoint in an environment that that allows systemcfg to be mapped it will not be restorable in an environment that forbids it.

This patch disables the mapping of systemcfg in checkpoint mode, which will force the omrtime functions to fall back to conventional Linux time APIs.

On Power `omrtime_current_time_millis` and `omrtime_hires_clock` can
use the timebase register to very quickly get the current time.
This requires mmapping the special `/proc/ppc64/systemcfg` file.

Some security modules (e.g. SELinux) prevent systemcfg from being mapped
by user processes. If we take a checkpoint in an environment that
that allows systemcfg to be mapped it will not be restorable in an
environment that forbids it.

This patch disables the mapping of systemcfg in checkpoint mode, which
will force the omrtime functions to fall back to conventional Linux time
APIs.

Signed-off-by: Younes Manton <[email protected]>
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