Skip to content

wishlist: add one more consideration to CLONE_PDIFD_AUTOKILL for PID 1 #54

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
Mar 11, 2026
Merged

wishlist: add one more consideration to CLONE_PDIFD_AUTOKILL for PID 1 #54

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
5 changes: 5 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -252,6 +252,11 @@ it with a pidfd right away. There are two possible approaches:
Permission checking would have to be strict. It should probably only be
allowed for the current thread-group leader on itself.

Note also that the kernel currently simply refuses to deliver `SIGKILL`
to PID 1 (global init). It will simply drop the signal. This will have
to be changed. Any implementation would also have to ensure that the
behavior post `SIGKILL` does not just involve freezing execution.

### inotify() events for BSD file locks

BSD file locks (i.e. `flock()`, as opposed to POSIX `F_SETLK` and
Expand Down
Loading