Changes in config

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/coredump/config

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/coredump/config

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/coredump/config

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/coredump/config

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/coredump/config

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/coredump/config

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/coredump/config

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/coredump/config

08c51f5bddc81c8c97c1eb11861b0dc009e5ccd8 - Merge drm/drm-next into drm-misc-n

Mon, 11 Aug 2025 14:37:45 +0200

Merge drm/drm-next into drm-misc-nUpdating drm-misc-next to the state of v6.17-rc1. Begins a new releasecycle.Signed-off-by: Thomas Zimmermann List of files: /linux/tools/testing/selftests/coredump/config

8d2b0853add1d7534dc0794e3c8e0b9e8c4ec640 - Merge drm/drm-fixes into drm-misc-fixes

Mon, 11 Aug 2025 16:49:06 +0200

Merge drm/drm-fixes into drm-misc-fixesUpdating drm-misc-fixes to the state of v6.17-rc1. Begins a new releasecycle.Signed-off-by: Thomas Zimmermann List of files: /linux/tools/testing/selftests/coredump/config

117eab5c6e31815649d952f6da03f67aa247d29b - Merge tag 'vfs-6.17-rc1.coredump' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs

Mon, 28 Jul 2025 20:50:36 +0200

Merge tag 'vfs-6.17-rc1.coredump' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfsPull coredump updates from Christian Brauner: "This contains an extension to the coredump socket and a proper rework of the coredump code. - This extends the coredump socket to allow the coredump server to tell the kernel how to process individual coredumps. This allows for fine-grained coredump management. Userspace can decide to just let the kernel write out the coredump, or generate the coredump itself, or just reject it. * COREDUMP_KERNEL The kernel will write the coredump data to the socket. * COREDUMP_USERSPACE The kernel will not write coredump data but will indicate to the parent that a coredump has been generated. This is used when userspace generates its own coredumps. * COREDUMP_REJECT The kernel will skip generating a coredump for this task. * COREDUMP_WAIT The kernel will prevent the task from exiting until the coredump server has shutdown the socket connection. The flexible coredump socket can be enabled by using the "@@" prefix instead of the single "@" prefix for the regular coredump socket: @@/run/systemd/coredump.socket - Cleanup the coredump code properly while we have to touch it anyway. Split out each coredump mode in a separate helper so it's easy to grasp what is going on and make the code easier to follow. The core coredump function should now be very trivial to follow"* tag 'vfs-6.17-rc1.coredump' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs: (31 commits) cleanup: add a scoped version of CLASS() coredump: add coredump_skip() helper coredump: avoid pointless variable coredump: order auto cleanup variables at the top coredump: add coredump_cleanup() coredump: auto cleanup prepare_creds() cred: add auto cleanup method coredump: directly return coredump: auto cleanup argv coredump: add coredump_write() coredump: use a single helper for the socket coredump: move pipe specific file check into coredump_pipe() coredump: split pipe coredumping into coredump_pipe() coredump: move core_pipe_count to global variable coredump: prepare to simplify exit paths coredump: split file coredumping into coredump_file() coredump: rename do_coredump() to vfs_coredump() selftests/coredump: make sure invalid paths are rejected coredump: validate socket path in coredump_parse() coredump: don't allow ".." in coredump socket path ... List of files: /linux/tools/testing/selftests/coredump/config

c8e7ce2aa11c1beb06ba7ccceb31396fd8d7464f - Merge patch series "coredump: allow for flexible coredump handling"

Wed, 04 Jun 2025 09:32:15 +0200

Merge patch series "coredump: allow for flexible coredump handling"Christian Brauner says:In addition to the extensive selftests I've already written a(non-production ready) simple Rust coredump server for this inuserspace:https://github.com/brauner/dumdum.gitExtend the coredump socket to allow the coredump server to tell thekernel how to process individual coredumps. This allows for fine-grainedcoredump management. Userspace can decide to just let the kernel writeout the coredump, or generate the coredump itself, or just reject it.When the crashing task connects to the coredump socket the kernel willsend a struct coredump_req to the coredump server. The kernel will setthe size member of struct coredump_req allowing the coredump server howmuch data can be read.The coredump server uses MSG_PEEK to peek the size of structcoredump_req. If the kernel uses a newer struct coredump_req thecoredump server just reads the size it knows and discard any remainingbytes in the buffer. If the kernel uses an older struct coredump_reqthe coredump server just reads the size the kernel knows.The returned struct coredump_req will inform the coredump server whatfeatures the kernel supports. The coredump_req->mask member is set tothe currently know features.The coredump server may only use features whose bits were raised by thekernel in coredump_req->mask.In response to a coredump_req from the kernel the coredump server sendsa struct coredump_ack to the kernel. The kernel informs the coredumpserver what version of struct coredump_ack it supports by setting structcoredump_req->size_ack to the size it knows about. The coredump servermay only send as many bytes as coredump_req->size_ack indicates (asmaller size is fine of course). The coredump server must setcoredump_ack->size accordingly.The coredump server sets the features it wants to use in structcoredump_ack->mask. Only bits returned in struct coredump_req->mask maybe used.In case an invalid struct coredump_ack is sent to the kernel a non-zerou32 integer is sent indicating the reason for the failure. If it wassuccessful a zero u32 integer is sent.In the initial version the following features are supported incoredump_{req,ack}->mask:* COREDUMP_KERNEL The kernel will write the coredump data to the socket.* COREDUMP_USERSPACE The kernel will not write coredump data but will indicate to the parent that a coredump has been generated. This is used when userspace generates its own coredumps.* COREDUMP_REJECT The kernel will skip generating a coredump for this task.* COREDUMP_WAIT The kernel will prevent the task from exiting until the coredump server has shutdown the socket connection.The flexible coredump socket can be enabled by using the "@@" prefixinstead of the single "@" prefix for the regular coredump socket: @@/run/systemd/coredump.socketwill enable flexible coredump handling. Current kernels already enforcethat "@" must be followed by "/" and will reject anything else. Soextending this is backward and forward compatible.Link: https://lore.kernel.org/20250603-work-coredump-socket-protocol-v2-0-05a5f0c18ecc@kernel.org* patches from https://lore.kernel.org/20250603-work-coredump-socket-protocol-v2-0-05a5f0c18ecc@kernel.org: selftests/coredump: add coredump server selftests tools: add coredump.h header selftests/coredump: cleanup coredump tests selftests/coredump: fix build coredump: allow for flexible coredump handlingSigned-off-by: Christian Brauner List of files: /linux/tools/testing/selftests/coredump/config

59cd658eaf404e3634624b25afc3233066bea34c - selftests/coredump: add coredump server selftests

Tue, 03 Jun 2025 15:31:59 +0200

selftests/coredump: add coredump server selftestsThis adds extensive tests for the coredump server.Link: https://lore.kernel.org/20250603-work-coredump-socket-protocol-v2-5-05a5f0c18ecc@kernel.orgAcked-by: Lennart Poettering Reviewed-by: Alexander Mikhalitsyn Signed-off-by: Christian Brauner List of files: /linux/tools/testing/selftests/coredump/config