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.
Showing the changes to include/uapi (1 of 2 files). Show all
Unified · Split
| @@ -26,9 +26,11 @@ · 25 unmodified lines | ||
| 26 | 26 | #define PIDFD_INFO_CGROUPID (1UL << 2) /* Always returned if available, even if not requested */ |
| 27 | 27 | #define PIDFD_INFO_EXIT (1UL << 3) /* Only returned if requested. */ |
| 28 | 28 | #define PIDFD_INFO_COREDUMP (1UL << 4) /* Only returned if requested. */ |
| 29 | +#define PIDFD_INFO_SUPPORTED_MASK (1UL << 5) /* Want/got supported mask flags */ | |
| 29 | 30 | |
| 30 | 31 | #define PIDFD_INFO_SIZE_VER0 64 /* sizeof first published struct */ |
| 31 | 32 | #define PIDFD_INFO_SIZE_VER1 72 /* sizeof second published struct */ |
| 33 | +#define PIDFD_INFO_SIZE_VER2 80 /* sizeof third published struct */ | |
| 32 | 34 | |
| 33 | 35 | /* |
| 34 | 36 | * Values for @coredump_mask in pidfd_info. |
| @@ -94,6 +96,7 @@ struct pidfd_info { · 59 unmodified lines | ||
| 94 | 96 | __s32 exit_code; |
| 95 | 97 | __u32 coredump_mask; |
| 96 | 98 | __u32 __spare1; |
| 99 | + __u64 supported_mask; /* Mask flags that this kernel supports */ | |
| 97 | 100 | }; |
| 98 | 101 | |
| 99 | 102 | #define PIDFS_IOCTL_MAGIC 0xFF |