Measure starting a program that needs an interpreter - #19
Merged
Conversation
openkal-linux could not start one AT ALL --- every `#!` script on every architecture --- and no suite anywhere looked, which is why it survived until a foreign binary made the same failure loud on aarch64.⚠️ THIS IMPLEMENTATION IS EXPECTED TO PASS AND IS CHECKED ANYWAY. It has no `execveat': it enters the directory and calls `execve' with a whole path, so the kernel never holds a name the interpreter cannot reopen. That is a reason to BELIEVE it works. Believing is exactly how the other one went unmeasured, and the reasoning that said "not ours" there was three true observations pointing the wrong way. Test-only; no behaviour changes and no version bump.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
openkal-linux could not start one AT ALL --- every
#!script on everyarchitecture --- and no suite anywhere looked, which is why it survived until a
foreign binary made the same failure loud on aarch64.
execveat': it enters the directory and callsexecve' with a whole path, so thekernel never holds a name the interpreter cannot reopen. That is a reason to
BELIEVE it works. Believing is exactly how the other one went unmeasured, and
the reasoning that said "not ours" there was three true observations pointing
the wrong way.
Test-only; no behaviour changes and no version bump.