Linux kernel stable tree (mirror) https://git.radix-linux.su/kernel/linux.git/atom?h=v6.6.131 2025-04-10T12:37:34+00:00 2025-04-10T12:37:34+00:00 Benjamin Berg benjamin.berg@intel.com 2025-02-10T16:09:26+00:00 urn:sha1:c9a6cf3fe680f555cae63959d5a732e3392a88d8 [ Upstream commit 84a6fc378471fbeaf48f8604566a5a33a3d63c18 ] There is no need to override the default version of this function anymore as UML now has proper _nofault memory access functions. Doing this also fixes the fact that the implementation was incorrect as using mincore() will incorrectly flag pages as inaccessible if they were swapped out by the host. Fixes: f75b1b1bedfb ("um: Implement probe_kernel_read()") Signed-off-by: Benjamin Berg <benjamin.berg@intel.com> Link: https://patch.msgid.link/20250210160926.420133-3-benjamin@sipsolutions.net Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Sasha Levin <sashal@kernel.org> 2019-09-15T19:37:17+00:00 Alex Dewar alex.dewar@gmx.co.uk 2019-08-25T09:49:18+00:00 urn:sha1:97870c34b453251cda9c2341f8534b78003a74dc Convert files to use SPDX header. All files are licensed under the GPLv2. Signed-off-by: Alex Dewar <alex.dewar@gmx.co.uk> Signed-off-by: Richard Weinberger <richard@nod.at> 2015-11-06T21:54:49+00:00 Anton Ivanov aivanov@brocade.com 2015-11-02T16:16:37+00:00 urn:sha1:2eb5f31bc4ea24bb293e82934cfa1cce9573304b UML is using an obsolete itimer call for all timers and "polls" for kernel space timer firing in its userspace portion resulting in a long list of bugs and incorrect behaviour(s). It also uses ITIMER_VIRTUAL for its timer which results in the timer being dependent on it running and the cpu load. This patch fixes this by moving to posix high resolution timers firing off CLOCK_MONOTONIC and relaying the timer correctly to the UML userspace. Fixes: - crashes when hosts suspends/resumes - broken userspace timers - effecive ~40Hz instead of what they should be. Note - this modifies skas behavior by no longer setting an itimer per clone(). Timer events are relayed instead. - kernel network packet scheduling disciplines - tcp behaviour especially under load - various timer related corner cases Finally, overall responsiveness of userspace is better. Signed-off-by: Thomas Meyer <thomas@m3y3r.de> Signed-off-by: Anton Ivanov <aivanov@brocade.com> [rw: massaged commit message] Signed-off-by: Richard Weinberger <richard@nod.at> 2015-04-13T19:00:53+00:00 Richard Weinberger richard@nod.at 2015-03-18T20:31:27+00:00 urn:sha1:d0b5e15f0c0fdd759dd3dd48dc2dc2e7199e0da0 Before we had SKAS0 UML had two modes of operation TT (tracing thread) and SKAS3/4 (separated kernel address space). TT was known to be insecure and got removed a long time ago. SKAS3/4 required a few (3 or 4) patches on the host side which never went mainline. The last host patch is 10 years old. With SKAS0 mode (separated kernel address space using 0 host patches), default since 2005, SKAS3/4 is obsolete and can be removed. Signed-off-by: Richard Weinberger <richard@nod.at> 2013-09-07T08:56:58+00:00 Richard Weinberger richard@nod.at 2013-08-18T11:30:08+00:00 urn:sha1:91d44ff860a9e9c0db81a89cbc24fa31fbd8e6d3 Richard reported that some UML processes survive if the UML main process receives a SIGTERM. This issue was caused by a wrongly placed signal(SIGTERM, SIG_DFL) in init_new_thread_signals(). It disabled the UML exit handler accidently for some processes. The correct solution is to disable the fatal handler for all UML helper threads/processes. Such that last_ditch_exit() does not get called multiple times and all processes can exit due to SIGTERM. Reported-and-tested-by: Richard W.M. Jones <rjones@redhat.com> Signed-off-by: Richard Weinberger <richard@nod.at> 2013-09-07T08:38:34+00:00 Richard Weinberger richard@nod.at 2013-08-17T16:46:00+00:00 urn:sha1:f75b1b1bedfb498cc43a992ce4d7ed8df3b1e770 UML needs it's own probe_kernel_read() to handle kernel mode faults correctly. The implementation uses mincore() on the host side to detect whether a page is owned by the UML kernel process. This fixes also a possible crash when sysrq-t is used. Starting with 3.10 sysrq-t calls probe_kernel_read() to read details from the kernel workers. As kernel worker are completely async pointers may turn NULL while reading them. Cc: <stian@nixia.no> Cc: <tj@kernel.org> Cc: <stable@vger.kernel.org> # 3.10.x Signed-off-by: Richard Weinberger <richard@nod.at> 2012-10-13T01:05:52+00:00 Linus Torvalds torvalds@linux-foundation.org 2012-10-13T01:05:52+00:00 urn:sha1:4e21fc138bfd7fe625ff5dc81541399aaf9d429b Pull third pile of kernel_execve() patches from Al Viro: "The last bits of infrastructure for kernel_thread() et.al., with alpha/arm/x86 use of those. Plus sanitizing the asm glue and do_notify_resume() on alpha, fixing the "disabled irq while running task_work stuff" breakage there. At that point the rest of kernel_thread/kernel_execve/sys_execve work can be done independently for different architectures. The only pending bits that do depend on having all architectures converted are restrictred to fs/* and kernel/* - that'll obviously have to wait for the next cycle. I thought we'd have to wait for all of them done before we start eliminating the longjump-style insanity in kernel_execve(), but it turned out there's a very simple way to do that without flagday-style changes." * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/signal: alpha: switch to saner kernel_execve() semantics arm: switch to saner kernel_execve() semantics x86, um: convert to saner kernel_execve() semantics infrastructure for saner ret_from_kernel_thread semantics make sure that kernel_thread() callbacks call do_exit() themselves make sure that we always have a return path from kernel_execve() ppc: eeh_event should just use kthread_run() don't bother with kernel_thread/kernel_execve for launching linuxrc alpha: get rid of switch_stack argument of do_work_pending() alpha: don't bother passing switch_stack separately from regs alpha: take SIGPENDING/NOTIFY_RESUME loop into signal.c alpha: simplify TIF_NEED_RESCHED handling 2012-10-12T17:35:22+00:00 Al Viro viro@zeniv.linux.org.uk 2012-10-11T01:35:42+00:00 urn:sha1:22e2430d60dbdfcdd732a086e9ef2dbd74c266d1 Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> 2012-10-09T20:28:45+00:00 Al Viro viro@ZenIV.linux.org.uk 2012-10-08T02:27:32+00:00 urn:sha1:37185b33240870719b6b5913a46e6a441f1ae96f Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Richard Weinberger <richard@nod.at> 2011-11-02T13:15:00+00:00 Al Viro viro@ftp.linux.org.uk 2011-08-18T19:05:29+00:00 urn:sha1:0de021f797e7bd785796071aab8e14827c87d6bf Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Richard Weinberger <richard@nod.at>