pyflame: fix the build on machines with kernel.yama.ptrace_scope > 0 #52828
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation for this change
This fixes #52827. cc'ing maintainer @symphorien for feedback.
Users of pyflame need to have
kernel.yama.ptrace_scope = 0
anyway, but it still seems useful for a machine with a hardened profile to be able to build it.I considered asking upstream to add some
skipIf
whenptrace_scope > 1
, but it doesn't look like they're working on pyflame right now.I tested this PR with
kernel.yama.ptrace_scope = 0
and= 1
:with
ptrace_scope = 0
:with
ptrace_scope = 1
:Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)