#systemd, #LXC, #LXD and a few other things.
👉 cfp.all-systems-go.io/all-systems-...
👉 cfp.all-systems-go.io/all-systems-...
(2) Is this useful for Bluetooth user space implementations?/Is this already used?
(3) Is it useful to also enable SO_PEERPIDFD for reaped peers for Bluetooth sockets?
And even if the current crashing thread isn't the actual thread-group leader we know that the thread-group leader cannot be reaped until all of its subthreads have exited.
And even if the current crashing thread isn't the actual thread-group leader we know that the thread-group leader cannot be reaped until all of its subthreads have exited.
We're installing a pidfd for the thread-group leader even if a subthread is calling do_coredump(). We know that task linkage hasn't been removed yet.
We're installing a pidfd for the thread-group leader even if a subthread is calling do_coredump(). We know that task linkage hasn't been removed yet.
Since usermode helpers are either children of the system_unbound_wq
workqueue or kthreadd we know that the file descriptor table is empty and can thus always use three as the file descriptor number.
Since usermode helpers are either children of the system_unbound_wq
workqueue or kthreadd we know that the file descriptor table is empty and can thus always use three as the file descriptor number.
When the usermode helper process is forked we install a pidfd file descriptor three into the usermode helper's file descriptor table so it's available to the exec'd program.
When the usermode helper process is forked we install a pidfd file descriptor three into the usermode helper's file descriptor table so it's available to the exec'd program.
There are tricky race-windows that cannot be easily closed by userspace. There's various ways like looking at the start time of a process to make sure that the usermode helper process is started
after the crashing process but it's all very very brittle and fraught with peril.
There are tricky race-windows that cannot be easily closed by userspace. There's various ways like looking at the start time of a process to make sure that the usermode helper process is started
after the crashing process but it's all very very brittle and fraught with peril.
Oh yeah, I already mentioned this a while ago but I also added support for pidfds in Linux coredumps.
/proc/sys/kernel/core_pattern has been extended so userspace can instruct the kernel to install a pidfd for the
crashing process into the usermode helper process, e.g., systemd-coredump.
Oh yeah, I already mentioned this a while ago but I also added support for pidfds in Linux coredumps.
/proc/sys/kernel/core_pattern has been extended so userspace can instruct the kernel to install a pidfd for the
crashing process into the usermode helper process, e.g., systemd-coredump.
web.git.kernel.org/pub/scm/linu...
web.git.kernel.org/pub/scm/linu...
github.com/util-linux/u...
This should be a nice performance improvement.
See brauner.io/2024/12/16/l... for some details on listmount() and statmount().
#linux #kernel
github.com/util-linux/u...
This should be a nice performance improvement.
See brauner.io/2024/12/16/l... for some details on listmount() and statmount().
#linux #kernel
containers: fosdem.org/2025/schedul...
kernel: fosdem.org/2025/schedul...
See you in Brussels!
containers: fosdem.org/2025/schedul...
kernel: fosdem.org/2025/schedul...
See you in Brussels!
brauner.io/2024/12/16/l...
#kernel #linux #vfs
brauner.io/2024/12/16/l...
#kernel #linux #vfs