From a38438529370ff66f747ab284f54a39c17ed4395 Mon Sep 17 00:00:00 2001 From: Christian Brauner Date: Mon, 9 Mar 2026 15:57:18 +0100 Subject: [PATCH] wishlist: add one more consideration to `CLONE_PDIFD_AUTOKILL` for PID 1 Signed-off-by: Christian Brauner --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index ce45731..8e3452b 100644 --- a/README.md +++ b/README.md @@ -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