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

How does proot support sysexit processing when seccomp starts?  #331

Open
w296488320 opened this issue May 2, 2022 · 1 comment
Open

Comments

@w296488320
Copy link

                /* Restore tracee's stack pointer now if it won't hit
   * the sysexit stage (i.e. when seccomp is enabled and
   * there's nothing else to do). 
   *  */
  if (tracee->restart_how == PTRACE_CONT) {
   suppressed_syscall_status = tracee->status;
   tracee->status = 0;
   poke_reg(tracee, STACK_POINTER, peek_reg(tracee, ORIGINAL, STACK_POINTER));
   
  }

I don't know why in seccomp mode to put the ( tracee->status = 0;)
This may not execute sysexit. Does it not support sysexit when seccomp is enabled?

@fh2002
Copy link

fh2002 commented Feb 22, 2023

PTRACE_SYSCALL

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants