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

Rework the status flag management of s390x. #106

Merged
merged 1 commit into from
Apr 30, 2021
Merged

Rework the status flag management of s390x. #106

merged 1 commit into from
Apr 30, 2021

Conversation

zherczeg
Copy link
Owner

I tested the patch with PCRE2, it worked.

@zherczeg zherczeg merged commit 1a1a517 into master Apr 30, 2021
@zherczeg zherczeg deleted the s390x_flags branch April 30, 2021 05:48
lrzlin pushed a commit to lrzlin/sljit-la that referenced this pull request Apr 14, 2024
When running under seccomp, sometimes sysexit handlers fail to execute.
This is possible when the first syscall a process makes,
before seccomp is enabled, gets handled in the SIGTRAP path.
However the conditions for this to occur seem fairly random,
so we fork out many processes to make it likely that at least
some hit this problem.

This problem may be related to issue zherczeg#106.
lrzlin pushed a commit to lrzlin/sljit-la that referenced this pull request Apr 14, 2024
sysexit events handler to be missed if sysenter is handled during
a syscall-enter-stop event instead of the seccomp ptrace event.

This may be a (at least partial) fix for issue zherczeg#106.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant