Commit 14296d0e authored Mar 08, 2025 by Ingo Molnar

Merge branch 'linus' into x86/urgent, to pick up dependent patches



Signed-off-by: Ingo Molnar <mingo@kernel.org>

parents 6914f7e2 21e4543a

.mailmap

+0 −1

Original line number	Diff line number	Diff line
		@@ -88,7 +88,6 @@ Antonio Quartulli <antonio@mandelbit.com> <antonio@open-mesh.com>
		Antonio Quartulli <antonio@mandelbit.com> <antonio.quartulli@open-mesh.com>
		Antonio Quartulli <antonio@mandelbit.com> <ordex@autistici.org>
		Antonio Quartulli <antonio@mandelbit.com> <ordex@ritirata.org>
		Antonio Quartulli <antonio@mandelbit.com> <antonio@openvpn.net>
		Antonio Quartulli <antonio@mandelbit.com> <a@unstable.cc>
		Anup Patel <anup@brainfault.org> <anup.patel@wdc.com>
		Archit Taneja <archit@ti.com>

Documentation/admin-guide/sysctl/kernel.rst

+11 −0

Original line number	Diff line number	Diff line
		@@ -212,6 +212,17 @@ pid>/``).
		This value defaults to 0.


		core_sort_vma
		=============

		The default coredump writes VMAs in address order. By setting
		``core_sort_vma`` to 1, VMAs will be written from smallest size
		to largest size. This is known to break at least elfutils, but
		can be handy when dealing with very large (and truncated)
		coredumps where the more useful debugging details are included
		in the smaller VMAs.


		core_uses_pid
		=============

Documentation/filesystems/idmappings.rst

+2 −2

Original line number	Diff line number	Diff line
		@@ -63,8 +63,8 @@ what id ``k11000`` corresponds to in the second or third idmapping. The
		straightforward algorithm to use is to apply the inverse of the first idmapping,
		mapping ``k11000`` up to ``u1000``. Afterwards, we can map ``u1000`` down using
		either the second idmapping mapping or third idmapping mapping. The second
		idmapping would map ``u1000`` down to ``21000``. The third idmapping would map
		``u1000`` down to ``u31000``.
		idmapping would map ``u1000`` down to ``k21000``. The third idmapping would map
		``u1000`` down to ``k31000``.

		If we were given the same task for the following three idmappings::

Documentation/scheduler/sched-rt-group.rst

+3 −0

Original line number	Diff line number	Diff line
		@@ -102,6 +102,9 @@ The system wide settings are configured under the /proc virtual file system:
		* sched_rt_period_us takes values from 1 to INT_MAX.
		* sched_rt_runtime_us takes values from -1 to sched_rt_period_us.
		* A run time of -1 specifies runtime == period, ie. no limit.
		* sched_rt_runtime_us/sched_rt_period_us > 0.05 inorder to preserve
		bandwidth for fair dl_server. For accurate value check average of
		runtime/period in /sys/kernel/debug/sched/fair_server/cpuX/


		2.2 Default behaviour

MAINTAINERS

+3 −0

Original line number	Diff line number	Diff line
		@@ -5775,6 +5775,7 @@ X: drivers/clk/clkdev.c

		COMMON INTERNET FILE SYSTEM CLIENT (CIFS and SMB3)
		M: Steve French <sfrench@samba.org>
		M: Steve French <smfrench@gmail.com>
		R: Paulo Alcantara <pc@manguebit.com> (DFS, global name space)
		R: Ronnie Sahlberg <ronniesahlberg@gmail.com> (directory leases, sparse files)
		R: Shyam Prasad N <sprasad@microsoft.com> (multichannel)
		@@ -12655,7 +12656,9 @@ F: tools/testing/selftests/

		KERNEL SMB3 SERVER (KSMBD)
		M: Namjae Jeon <linkinjeon@kernel.org>
		M: Namjae Jeon <linkinjeon@samba.org>
		M: Steve French <sfrench@samba.org>
		M: Steve French <smfrench@gmail.com>
		R: Sergey Senozhatsky <senozhatsky@chromium.org>
		R: Tom Talpey <tom@talpey.com>
		L: linux-cifs@vger.kernel.org