Intel OpenBMC Linux kernel source tree (mirror) https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev 2015-05-31T11:14:07+00:00 2015-05-31T11:14:07+00:00 Nicolas Iooss nicolas.iooss_linux@m4x.org 2014-10-12T11:02:13+00:00 urn:sha1:5f32943b5e9a48bf3269430e1a7a210411e0cc98 When declaring __syscall_stub_start, use the same type in UML userspace code as in arch/um/include/asm/sections.h. While at it, also declare batch_syscall_stub as char[]. Signed-off-by: Nicolas Iooss <nicolas.iooss_linux@m4x.org> Signed-off-by: Richard Weinberger <richard@nod.at> 2015-04-13T19:17:44+00:00 Thomas Meyer thomas@m3y3r.de 2015-03-28T08:59:46+00:00 urn:sha1:33bbc3065414722065a20cbdbeaf352173e72f39 atomic_notifier_chain_register() and uml_postsetup() do call kernel code that rely on the "current" kernel macro and a valid task_struct resp. thread_info struct. Give those functions a valid stack by moving uml_postsetup() in the init_thread stack. This moves enables a panic() call in this early code to generate a valid stacktrace, instead of crashing. E.g. when an UML kernel is started with an initrd but too few physical memory the panic() call get's actually processed. Signed-off-by: Thomas Meyer <thomas@m3y3r.de> 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> 2014-07-20T10:56:34+00:00 Richard Weinberger richard@nod.at 2014-07-20T10:56:34+00:00 urn:sha1:ae5db6d12341684913a78b6537c0b9c22c999b5c This reverts commit 0974a9cadc7886f7baaa458bb0c89f5c5f9d458e. The real for for that issue is to release current->mm->mmap_sem in fix_range_common(). Signed-off-by: Richard Weinberger <richard@nod.at> 2013-07-19T09:31:36+00:00 Richard Weinberger richard@nod.at 2013-07-19T09:31:36+00:00 urn:sha1:9a8c1359571c5d5e2fbc43cf457a6486b70a70cb Currently we use both struct siginfo and siginfo_t. Let's use struct siginfo internally to avoid ongoing compiler warning. We are allowed to do so because struct siginfo and siginfo_t are equivalent. Signed-off-by: Richard Weinberger <richard@nod.at> 2013-07-19T08:45:18+00:00 Richard Weinberger richard@nod.at 2013-05-17T12:21:01+00:00 urn:sha1:0974a9cadc7886f7baaa458bb0c89f5c5f9d458e If we die within a stub handler we only way to reliable kill the (obviously) dying uml guest process is killing it's host twin on the host side. Signed-off-by: Richard Weinberger <richard@nod.at> 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> 2012-08-01T22:49:17+00:00 Martin Pärtel martin.partel@gmail.com 2012-08-01T22:49:17+00:00 urn:sha1:d3c1cfcdb43e023ab1b1c7a555cd9e929026500a UML guest processes now get correct siginfo_t for SIGTRAP, SIGFPE, SIGILL and SIGBUS. Specifically, si_addr and si_code are now correct where previously they were si_addr = NULL and si_code = 128. Signed-off-by: Martin Pärtel <martin.partel@gmail.com> Signed-off-by: Richard Weinberger <richard@nod.at> 2012-08-01T22:25:44+00:00 Al Viro viro@zeniv.linux.org.uk 2012-05-23T04:25:15+00:00 urn:sha1:b8a420952336ed81ef5c9bf8bad90d3deaee5521 Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Richard Weinberger <richard@nod.at> 2012-05-21T19:09:32+00:00 Richard Weinberger richard@nod.at 2012-04-13T13:37:57+00:00 urn:sha1:54ce9256ad705ae8b628edfadce161aa7099922d Signed-off-by: Richard Weinberger <richard@nod.at>