diff options
| author | Christian Brauner <brauner@kernel.org> | 2025-10-28 09:45:50 +0100 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2025-10-30 14:25:13 +0100 |
| commit | dfd78546c95330db2252e0d7e937a15ab5eddb4e (patch) | |
| tree | 0d5a15a3e5469213567f5d366be399459db1dbce /net/unix/af_unix.c | |
| parent | d8fc51d8fa3b9894713e7eebcf574bee488fa3e1 (diff) | |
pidfd: add a new supported_mask field
Some of the future fields in struct pidfd_info can be optional. If the
kernel has nothing to emit in that field, then it doesn't set the flag
in the reply. This presents a problem: There is currently no way to know
what mask flags the kernel supports since one can't always count on them
being in the reply.
Add a new PIDFD_INFO_SUPPORTED_MASK flag and field that the kernel can
set in the reply. Userspace can use this to determine if the fields it
requires from the kernel are supported. This also gives us a way to
deprecate fields in the future, if that should become necessary.
Link: https://patch.msgid.link/20251028-work-coredump-signal-v1-5-ca449b7b7aa0@kernel.org
Reviewed-by: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>
Reviewed-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions
