Changes in Makefile

7a0e692a0381254b2f77c54dec100cd3325a6fdf - Merge branch 'next' into for-linus

Tue, 23 Jun 2026 08:10:08 +0200

Merge branch 'next' into for-linusPrepare input updates for 7.2 merge window. List of files: /linux/tools/testing/selftests/pidfd/Makefile

fff88709f9a9153af85b5224b4594caa5387ca60 - Merge tag 'v7.1-rc6' into next

Mon, 01 Jun 2026 04:43:25 +0200

Merge tag 'v7.1-rc6' into nextSync up with mainline to pull in a fix to IMS PCU driver and otherenhancements. List of files: /linux/tools/testing/selftests/pidfd/Makefile

5c8cbca290acdd49a694b36c0af76ba0c00bbf12 - Merge branch '20260507-ubwc-rework-v4-4-c19593d20c1d@oss.qualcomm.com' of https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux into HEAD

Thu, 21 May 2026 22:36:50 +0200

Merge branch '20260507-ubwc-rework-v4-4-c19593d20c1d@oss.qualcomm.com' of https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux into HEADMerge the branch with the soc/qcom changes, required for the next UBWCpatches.Signed-off-by: Dmitry Baryshkov List of files: /linux/tools/testing/selftests/pidfd/Makefile

09d6818d3bdc1ea6e49a425040528cbdbc97bc0a - Merge branch 'linus' into timers/clocksource

Mon, 18 May 2026 11:01:07 +0200

Merge branch 'linus' into timers/clocksource... to bring it up to date for new changes. List of files: /linux/tools/testing/selftests/pidfd/Makefile

658a6021492ad3b1b8a6e9a83963a1fad35a2af8 - Merge drm/drm-next into drm-intel-next

Fri, 15 May 2026 13:01:15 +0200

Merge drm/drm-next into drm-intel-nextSome Display Port Adaptive Sync depends on drm work.Signed-off-by: Rodrigo Vivi List of files: /linux/tools/testing/selftests/pidfd/Makefile

8edf8b09fc44990977b3fbcb708035b1740d0b7e - Merge drm/drm-next into drm-intel-gt-next

Tue, 12 May 2026 10:16:35 +0200

Merge drm/drm-next into drm-intel-gt-nextBackmerging to pull in commit 5401b9adebc9 ("i915: don't usea vma that didn't match the context VM") to revert it.Signed-off-by: Joonas Lahtinen List of files: /linux/tools/testing/selftests/pidfd/Makefile

c53ed3e99920df6a90553c89a1c053aa0776841e - Merge drm/drm-next into drm-xe-next

Fri, 08 May 2026 16:19:45 +0200

Merge drm/drm-next into drm-xe-nextBringing in recent display changes.Signed-off-by: Thomas Hellström List of files: /linux/tools/testing/selftests/pidfd/Makefile

cafac16b6207b88ad92fbba1169ae4f43865cb0d - Merge drm/drm-next into drm-misc-next

Mon, 27 Apr 2026 10:49:13 +0200

Merge drm/drm-next into drm-misc-nextGetting fixes and updates from v7.1-rc1.Signed-off-by: Thomas Zimmermann List of files: /linux/tools/testing/selftests/pidfd/Makefile

0fc8f6200d2313278fbf4539bbab74677c685531 - Merge drm/drm-fixes into drm-misc-fixes

Mon, 27 Apr 2026 10:26:49 +0200

Merge drm/drm-fixes into drm-misc-fixesGetting fixes and updates from v7.1-rc1.Signed-off-by: Thomas Zimmermann List of files: /linux/tools/testing/selftests/pidfd/Makefile

07c3ef58223e2c75ea209d8c416b976ec30d9413 - Merge tag 'vfs-7.1-rc1.pidfs' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs

Mon, 13 Apr 2026 22:27:11 +0200

Merge tag 'vfs-7.1-rc1.pidfs' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfsPull clone and pidfs updates from Christian Brauner: "Add three new clone3() flags for pidfd-based process lifecycle management. CLONE_AUTOREAP: CLONE_AUTOREAP makes a child process auto-reap on exit without ever becoming a zombie. This is a per-process property in contrast to the existing auto-reap mechanism via SA_NOCLDWAIT or SIG_IGN for SIGCHLD which applies to all children of a given parent. Currently the only way to automatically reap children is to set SA_NOCLDWAIT or SIG_IGN on SIGCHLD. This is a parent-scoped property affecting all children which makes it unsuitable for libraries or applications that need selective auto-reaping of specific children while still being able to wait() on others. CLONE_AUTOREAP stores an autoreap flag in the child's signal_struct. When the child exits do_notify_parent() checks this flag and causes exit_notify() to transition the task directly to EXIT_DEAD. Since the flag lives on the child it survives reparenting: if the original parent exits and the child is reparented to a subreaper or init the child still auto-reaps when it eventually exits. This is cleaner than forcing the subreaper to get SIGCHLD and then reaping it. If the parent doesn't care the subreaper won't care. If there's a subreaper that would care it would be easy enough to add a prctl() that either just turns back on SIGCHLD and turns off auto-reaping or a prctl() that just notifies the subreaper whenever a child is reparented to it. CLONE_AUTOREAP can be combined with CLONE_PIDFD to allow the parent to monitor the child's exit via poll() and retrieve exit status via PIDFD_GET_INFO. Without CLONE_PIDFD it provides a fire-and-forget pattern. No exit signal is delivered so exit_signal must be zero. CLONE_THREAD and CLONE_PARENT are rejected: CLONE_THREAD because autoreap is a process-level property, and CLONE_PARENT because an autoreap child reparented via CLONE_PARENT could become an invisible zombie under a parent that never calls wait(). The flag is not inherited by the autoreap process's own children. Each child that should be autoreaped must be explicitly created with CLONE_AUTOREAP. CLONE_NNP: CLONE_NNP sets no_new_privs on the child at clone time. Unlike prctl(PR_SET_NO_NEW_PRIVS) which a process sets on itself, CLONE_NNP allows the parent to impose no_new_privs on the child at creation without affecting the parent's own privileges. CLONE_THREAD is rejected because threads share credentials. CLONE_NNP is useful on its own for any spawn-and-sandbox pattern but was specifically introduced to enable unprivileged usage of CLONE_PIDFD_AUTOKILL. CLONE_PIDFD_AUTOKILL: This flag ties a child's lifetime to the pidfd returned from clone3(). When the last reference to the struct file created by clone3() is closed the kernel sends SIGKILL to the child. A pidfd obtained via pidfd_open() for the same process does not keep the child alive and does not trigger autokill - only the specific struct file from clone3() has this property. This is useful for container runtimes, service managers, and sandboxed subprocess execution - any scenario where the child must die if the parent crashes or abandons the pidfd or just wants a throwaway helper process. CLONE_PIDFD_AUTOKILL requires both CLONE_PIDFD and CLONE_AUTOREAP. It requires CLONE_PIDFD because the whole point is tying the child's lifetime to the pidfd. It requires CLONE_AUTOREAP because a killed child with no one to reap it would become a zombie - the primary use case is the parent crashing or abandoning the pidfd so no one is around to call waitpid(). CLONE_THREAD is rejected because autokill targets a process not a thread. If CLONE_NNP is specified together with CLONE_PIDFD_AUTOKILL an unprivileged user may spawn a process that is autokilled. The child cannot escalate privileges via setuid/setgid exec after being spawned. If CLONE_PIDFD_AUTOKILL is specified without CLONE_NNP the caller must have have CAP_SYS_ADMIN in its user namespace"* tag 'vfs-7.1-rc1.pidfs' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs: selftests: check pidfd_info->coredump_code correctness pidfds: add coredump_code field to pidfd_info kselftest/coredump: reintroduce null pointer dereference selftests/pidfd: add CLONE_PIDFD_AUTOKILL tests selftests/pidfd: add CLONE_NNP tests selftests/pidfd: add CLONE_AUTOREAP tests pidfd: add CLONE_PIDFD_AUTOKILL clone: add CLONE_NNP clone: add CLONE_AUTOREAP List of files: /linux/tools/testing/selftests/pidfd/Makefile

a2900f5aa4e7724a2bf56ddb1a4f816d4fcc0598 - Merge patch series "pidfd: add CLONE_AUTOREAP, CLONE_NNP, and CLONE_PIDFD_AUTOKILL"

Wed, 11 Mar 2026 23:24:31 +0100

Merge patch series "pidfd: add CLONE_AUTOREAP, CLONE_NNP, and CLONE_PIDFD_AUTOKILL"Christian Brauner says:Add three new clone3() flags for pidfd-based process lifecyclemanagement.=== CLONE_AUTOREAP ===CLONE_AUTOREAP makes a child process auto-reap on exit without everbecoming a zombie. This is a per-process property in contrast to theexisting auto-reap mechanism via SA_NOCLDWAIT or SIG_IGN for SIGCHLDwhich applies to all children of a given parent.Currently the only way to automatically reap children is to setSA_NOCLDWAIT or SIG_IGN on SIGCHLD. This is a parent-scoped propertyaffecting all children which makes it unsuitable for libraries orapplications that need selective auto-reaping of specific children whilestill being able to wait() on others.CLONE_AUTOREAP stores an autoreap flag in the child's signal_struct.When the child exits do_notify_parent() checks this flag and causesexit_notify() to transition the task directly to EXIT_DEAD. Since theflag lives on the child it survives reparenting: if the original parentexits and the child is reparented to a subreaper or init the child stillauto-reaps when it eventually exits. This is cleaner than forcing thesubreaper to get SIGCHLD and then reaping it. If the parent doesn't carethe subreaper won't care. If there's a subreaper that would care itwould be easy enough to add a prctl() that either just turns back onSIGCHLD and turns off auto-reaping or a prctl() that just notifies thesubreaper whenever a child is reparented to it.CLONE_AUTOREAP can be combined with CLONE_PIDFD to allow the parent tomonitor the child's exit via poll() and retrieve exit status viaPIDFD_GET_INFO. Without CLONE_PIDFD it provides a fire-and-forgetpattern. No exit signal is delivered so exit_signal must be zero.CLONE_THREAD and CLONE_PARENT are rejected: CLONE_THREAD becauseautoreap is a process-level property, and CLONE_PARENT because anautoreap child reparented via CLONE_PARENT could become an invisiblezombie under a parent that never calls wait().The flag is not inherited by the autoreap process's own children. Eachchild that should be autoreaped must be explicitly created withCLONE_AUTOREAP.=== CLONE_NNP ===CLONE_NNP sets no_new_privs on the child at clone time. Unlikeprctl(PR_SET_NO_NEW_PRIVS) which a process sets on itself, CLONE_NNPallows the parent to impose no_new_privs on the child at creationwithout affecting the parent's own privileges. CLONE_THREAD is rejectedbecause threads share credentials. CLONE_NNP is useful on its own forany spawn-and-sandbox pattern but was specifically introduced to enableunprivileged usage of CLONE_PIDFD_AUTOKILL.=== CLONE_PIDFD_AUTOKILL ===This flag ties a child's lifetime to the pidfd returned from clone3().When the last reference to the struct file created by clone3() is closedthe kernel sends SIGKILL to the child. A pidfd obtained via pidfd_open()for the same process does not keep the child alive and does not triggerautokill - only the specific struct file from clone3() has thisproperty. This is useful for container runtimes, service managers, andsandboxed subprocess execution - any scenario where the child must dieif the parent crashes or abandons the pidfd or just wants a throwawayhelper process.CLONE_PIDFD_AUTOKILL requires both CLONE_PIDFD and CLONE_AUTOREAP. Itrequires CLONE_PIDFD because the whole point is tying the child'slifetime to the pidfd. It requires CLONE_AUTOREAP because a killed childwith no one to reap it would become a zombie - the primary use case isthe parent crashing or abandoning the pidfd so no one is around to callwaitpid(). CLONE_THREAD is rejected because autokill targets a processnot a thread.If CLONE_NNP is specified together with CLONE_PIDFD_AUTOKILL anunprivileged user may spawn a process that is autokilled. The childcannot escalate privileges via setuid/setgid exec after being spawned.If CLONE_PIDFD_AUTOKILL is specified without CLONE_NNP the caller musthave have CAP_SYS_ADMIN in its user namespace.* patches from https://patch.msgid.link/20260226-work-pidfs-autoreap-v5-0-d148b984a989@kernel.org: selftests/pidfd: add CLONE_PIDFD_AUTOKILL tests selftests/pidfd: add CLONE_NNP tests selftests/pidfd: add CLONE_AUTOREAP tests pidfd: add CLONE_PIDFD_AUTOKILL clone: add CLONE_NNP clone: add CLONE_AUTOREAPLink: https://patch.msgid.link/20260226-work-pidfs-autoreap-v5-0-d148b984a989@kernel.orgSigned-off-by: Christian Brauner List of files: /linux/tools/testing/selftests/pidfd/Makefile

76d46ad2c52a4d7631274a35777ac4601103e2aa - selftests/pidfd: add CLONE_AUTOREAP tests

Thu, 26 Feb 2026 14:51:02 +0100

selftests/pidfd: add CLONE_AUTOREAP testsAdd tests for the new CLONE_AUTOREAP clone3() flag:- autoreap_without_pidfd: CLONE_AUTOREAP without CLONE_PIDFD works (fire-and-forget)- autoreap_rejects_exit_signal: CLONE_AUTOREAP with non-zero exit_signal fails- autoreap_rejects_parent: CLONE_AUTOREAP with CLONE_PARENT fails- autoreap_rejects_thread: CLONE_AUTOREAP with CLONE_THREAD fails- autoreap_basic: child exits, pidfd poll works, PIDFD_GET_INFO returns correct exit code, waitpid() returns -ECHILD- autoreap_signaled: child killed by signal, exit info correct via pidfd- autoreap_reparent: autoreap grandchild reparented to subreaper still auto-reaps- autoreap_multithreaded: autoreap process with sub-threads auto-reaps after last thread exits- autoreap_no_inherit: grandchild forked without CLONE_AUTOREAP becomes a regular zombieLink: https://patch.msgid.link/20260226-work-pidfs-autoreap-v5-4-d148b984a989@kernel.orgSigned-off-by: Christian Brauner List of files: /linux/tools/testing/selftests/pidfd/Makefile

cb9f145f638d7afa633632a9290d6ad06caeb8ee - Merge remote-tracking branch 'drm/drm-next' into msm-next-robclark

Sat, 01 Nov 2025 13:47:30 +0100

Merge remote-tracking branch 'drm/drm-next' into msm-next-robclarkBack-merge drm-next to get caught up.Signed-off-by: Rob Clark List of files: /linux/tools/testing/selftests/pidfd/Makefile

f088104d837a991c65e51fa30bb4196169b3244d - Merge drm/drm-next into drm-intel-gt-next

Tue, 16 Sep 2025 12:53:20 +0200

Merge drm/drm-next into drm-intel-gt-nextBackmerge in order to get the commit: 048832a3f400 ("drm/i915: Refactor shmem_pwrite() to use kiocb and write_iter")To drm-intel-gt-next as there are followup fixes to be applied.Signed-off-by: Joonas Lahtinen List of files: /linux/tools/testing/selftests/pidfd/Makefile

a53d0cf7f1cb3182ad533ff5cacfa5fd29c419ad - Merge commit 'linus' into core/bugs, to resolve conflicts

Tue, 05 Aug 2025 11:15:34 +0200

Merge commit 'linus' into core/bugs, to resolve conflictsResolve conflicts with this commit that was developed in parallelduring the merge window: 8c8efa93db68 ("x86/bug: Add ARCH_WARN_ASM macro for BUG/WARN asm code sharing with Rust") Conflicts: arch/riscv/include/asm/bug.h arch/x86/include/asm/bug.hSigned-off-by: Ingo Molnar List of files: /linux/tools/testing/selftests/pidfd/Makefile

8b87f67b4c87452e21721887fa8dec1f4c6b2b7c - Merge branch 'next' into for-linus

Wed, 08 Oct 2025 06:53:13 +0200

Merge branch 'next' into for-linusPrepare input updates for 6.18 merge window. List of files: /linux/tools/testing/selftests/pidfd/Makefile

4b051897df2375414587a245ecb9bb1a4d26b3b8 - Merge tag 'v6.17-rc2' into HEAD

Thu, 21 Aug 2025 20:46:49 +0200

Merge tag 'v6.17-rc2' into HEADSync up with mainline to bring in changes to include/linux/sprintf.h List of files: /linux/tools/testing/selftests/pidfd/Makefile

b4d90dbc4c1bc4bd3eb2d2989330af0eb95c98e8 - Merge drm/drm-next into drm-misc-next-fixes

Mon, 15 Sep 2025 10:23:28 +0200

Merge drm/drm-next into drm-misc-next-fixesBackmerging to drm-misc-next-fixes to get features and fixes fromv6.17-rc6.Signed-off-by: Thomas Zimmermann List of files: /linux/tools/testing/selftests/pidfd/Makefile

702fdf3513b045f596f836d9a4b8672c76f11834 - Merge drm/drm-next into drm-intel-next

Wed, 10 Sep 2025 14:01:42 +0200

Merge drm/drm-next into drm-intel-nextCatching up with some display dependencies.Signed-off-by: Rodrigo Vivi List of files: /linux/tools/testing/selftests/pidfd/Makefile

ca994e8922f25f7fed2075098f185cf198109eaa - Merge drm/drm-next into drm-xe-next

Tue, 12 Aug 2025 14:58:37 +0200

Merge drm/drm-next into drm-xe-nextBring v6.17-rc1 to propagate commits from other subsystems, particularlyPCI, which has some new functions needed for SR-IOV integration.Signed-off-by: Lucas De Marchi List of files: /linux/tools/testing/selftests/pidfd/Makefile