Pidfd: Revision history

13 March 2024

• curprev 10:3010:30, 13 March 2024‎ Dank talk contribs‎ 3,277 bytes +160‎ →‎Kernel
• curprev 10:2710:27, 13 March 2024‎ Dank talk contribs‎ 3,117 bytes +76‎ →‎See also
• curprev 10:2710:27, 13 March 2024‎ Dank talk contribs‎ 3,041 bytes +86‎ →‎Kernel

7 February 2024

• curprev 03:1203:12, 7 February 2024‎ Dank talk contribs‎ 2,955 bytes 0‎ →‎See also
• curprev 02:2302:23, 7 February 2024‎ Dank talk contribs‎ 2,955 bytes +124‎ →‎Glibc
• curprev 02:2102:21, 7 February 2024‎ Dank talk contribs‎ 2,831 bytes +76‎ →‎Glibc
• curprev 02:2002:20, 7 February 2024‎ Dank talk contribs‎ 2,755 bytes +559‎ No edit summary

1 July 2023

• curprev 01:4601:46, 1 July 2023‎ Dank talk contribs‎ 2,196 bytes +21‎ No edit summary
• curprev 01:4601:46, 1 July 2023‎ Dank talk contribs‎ 2,175 bytes +373‎ No edit summary

30 June 2023

• curprev 19:4719:47, 30 June 2023‎ Dank talk contribs‎ 1,802 bytes +993‎ No edit summary
• curprev 19:1119:11, 30 June 2023‎ Dank talk contribs‎ 809 bytes +1‎ No edit summary
• curprev 19:1019:10, 30 June 2023‎ Dank talk contribs‎ 808 bytes +808‎ Created page with "Since Linux 5.2, pidfds have more or less allowed one to refer to a process using a file descriptor, making it possible to eliminate a set of race conditions and ambiguities. At the heart of the pidfd abstraction is the <tt>CLONE_PIDFD</tt> flag to the <tt>clone(2)</tt> system call (note that this recycles the deprecated <tt>CLONE_PID</tt> bit). It is not possible to use this flag with <tt>CLONE_THREAD</tt>, and thus the created process will always be a t..."