1734a4ad6b
It is useful to be able to utilise the pidfd mechanism to reference the current thread or process (from a userland point of view - thread group leader from the kernel's point of view). Therefore introduce PIDFD_SELF_THREAD to refer to the current thread, and PIDFD_SELF_THREAD_GROUP to refer to the current thread group leader. For convenience and to avoid confusion from userland's perspective we alias these: * PIDFD_SELF is an alias for PIDFD_SELF_THREAD - This is nearly always what the user will want to use, as they would find it surprising if for instance fd's were unshared()'d and they wanted to invoke pidfd_getfd() and that failed. * PIDFD_SELF_PROCESS is an alias for PIDFD_SELF_THREAD_GROUP - Most users have no concept of thread groups or what a thread group leader is, and from userland's perspective and nomenclature this is what userland considers to be a process. We adjust pidfd_get_task() and the pidfd_send_signal() system call with specific handling for this, implementing this functionality for process_madvise(), process_mrelease() (albeit, using it here wouldn't really make sense) and pidfd_send_signal(). Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com> Link: https://lore.kernel.org/r/24315a16a3d01a548dd45c7515f7d51c767e954e.1738268370.git.lorenzo.stoakes@oracle.com Signed-off-by: Christian Brauner <brauner@kernel.org> (cherry picked from commit f08d0c3a71114bb36d1722506d926bd497182781) [surenb: trivial merge conflict in pidfd.h, adjusted pidfd_send_signal() code for differences between 6.12 and upstream] Bug: 402449065 Change-Id: I98e7c16b20ffe04b95248d8ae865c10c1150d058 Signed-off-by: Suren Baghdasaryan <surenb@google.com>
57 lines
2.2 KiB
C
57 lines
2.2 KiB
C
/* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
|
|
|
|
#ifndef _UAPI_LINUX_PIDFD_H
|
|
#define _UAPI_LINUX_PIDFD_H
|
|
|
|
#include <linux/types.h>
|
|
#include <linux/fcntl.h>
|
|
#include <linux/ioctl.h>
|
|
|
|
/* Flags for pidfd_open(). */
|
|
#define PIDFD_NONBLOCK O_NONBLOCK
|
|
#define PIDFD_THREAD O_EXCL
|
|
|
|
/* Flags for pidfd_send_signal(). */
|
|
#define PIDFD_SIGNAL_THREAD (1UL << 0)
|
|
#define PIDFD_SIGNAL_THREAD_GROUP (1UL << 1)
|
|
#define PIDFD_SIGNAL_PROCESS_GROUP (1UL << 2)
|
|
|
|
#define PIDFS_IOCTL_MAGIC 0xFF
|
|
|
|
#define PIDFD_GET_CGROUP_NAMESPACE _IO(PIDFS_IOCTL_MAGIC, 1)
|
|
#define PIDFD_GET_IPC_NAMESPACE _IO(PIDFS_IOCTL_MAGIC, 2)
|
|
#define PIDFD_GET_MNT_NAMESPACE _IO(PIDFS_IOCTL_MAGIC, 3)
|
|
#define PIDFD_GET_NET_NAMESPACE _IO(PIDFS_IOCTL_MAGIC, 4)
|
|
#define PIDFD_GET_PID_NAMESPACE _IO(PIDFS_IOCTL_MAGIC, 5)
|
|
#define PIDFD_GET_PID_FOR_CHILDREN_NAMESPACE _IO(PIDFS_IOCTL_MAGIC, 6)
|
|
#define PIDFD_GET_TIME_NAMESPACE _IO(PIDFS_IOCTL_MAGIC, 7)
|
|
#define PIDFD_GET_TIME_FOR_CHILDREN_NAMESPACE _IO(PIDFS_IOCTL_MAGIC, 8)
|
|
#define PIDFD_GET_USER_NAMESPACE _IO(PIDFS_IOCTL_MAGIC, 9)
|
|
#define PIDFD_GET_UTS_NAMESPACE _IO(PIDFS_IOCTL_MAGIC, 10)
|
|
|
|
/*
|
|
* The concept of process and threads in userland and the kernel is a confusing
|
|
* one - within the kernel every thread is a 'task' with its own individual PID,
|
|
* however from userland's point of view threads are grouped by a single PID,
|
|
* which is that of the 'thread group leader', typically the first thread
|
|
* spawned.
|
|
*
|
|
* To cut the Gideon knot, for internal kernel usage, we refer to
|
|
* PIDFD_SELF_THREAD to refer to the current thread (or task from a kernel
|
|
* perspective), and PIDFD_SELF_THREAD_GROUP to refer to the current thread
|
|
* group leader...
|
|
*/
|
|
#define PIDFD_SELF_THREAD -10000 /* Current thread. */
|
|
#define PIDFD_SELF_THREAD_GROUP -20000 /* Current thread group leader. */
|
|
|
|
/*
|
|
* ...and for userland we make life simpler - PIDFD_SELF refers to the current
|
|
* thread, PIDFD_SELF_PROCESS refers to the process thread group leader.
|
|
*
|
|
* For nearly all practical uses, a user will want to use PIDFD_SELF.
|
|
*/
|
|
#define PIDFD_SELF PIDFD_SELF_THREAD
|
|
#define PIDFD_SELF_PROCESS PIDFD_SELF_THREAD_GROUP
|
|
|
|
#endif /* _UAPI_LINUX_PIDFD_H */
|