Skip to content

wishlist: exit_signal system call #60

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.

Sign up for GitHub

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

Merged
keszybz merged 1 commit into from
Sep 29, 2026
Merged

wishlist: exit_signal system call #60

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -823,6 +823,22 @@ tells userspace that there was an fd, but it was not allowed through.

**Use-Case:** Any code that wants to use `SCM_RIGHTS` properly.

### Exit process with a signal regardless of signal handler disposition

A race-free implementation of `abort` is difficult because it may
become necessary to change the `SIGABRT` signal handler disposition to
`SIG_DFL` if the signal handler returns. (The changed signal handler
disposition may be incorrectly observed by a concurrent `execve`.)
Having an `exit_signal` system call that terminates the process with
the signal, regardless of disposition, would solve this issue.

For the same reason, application crash handlers currently struggle
with preserving the triggering signal, so that the invoking process
receives notification that a signal happened. An `exit_signal` system
call could help here, too.

**Use-Case:** Any application that wants to terminate with a signal.

---

## Finished Items
Expand Down