From: Richard Weinberger Subject: Re: [uml-devel] trinity commit 23dc478aba breaks syscall "mremap" at a 32 bit user mode linux Date: Fri, 02 May 2014 09:21:09 +0200 Message-ID: <53634765.6060000@nod.at> References: <53613E96.2030006@gmx.de> <536221F4.6000405@gmx.de> <53623EFE.3040603@nod.at> <5362651A.1020504@gmx.de> <5362B53E.5060601@nod.at> <5362BDD1.9070105@gmx.de> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <5362BDD1.9070105@gmx.de> Sender: trinity-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="iso-8859-1" To: =?UTF-8?B?VG9yYWxmIEbDtnJzdGVy?= Cc: trinity@vger.kernel.org, UML devel Am 01.05.2014 23:34, schrieb Toralf F=C3=B6rster: > On 05/01/2014 10:57 PM, Richard Weinberger wrote: >> Toralf, >> >> Yeah, this is because trinity destroys the UML stub code. >> Please test the attached patch, it should fix the root cause of the = problem. >> >> Thanks, >> //richard >> >=20 > If I do just apply fix2.patch onto latest git tree v3.15-rc3-113-gba= 6728f then I do get after a while : >=20 > * Starting sshd ... = [ ok ] > * Starting local > net.core.warnings =3D 0 = [ ok ] > Kernel panic - not syncing: do_syscall_stub : PTRACE_SETREGS failed, = errno =3D 3 >=20 > CPU: 0 PID: 1728 Comm: trinity-c0 Not tainted 3.15.0-rc3-00113-gba672= 8f-dirty #5 > Stack: > BUG: soft lockup - CPU#0 stuck for 22s! [trinity-c0:1728] >=20 > EIP: c500:[<47c6cf00>] CPU: 0 Not tainted EFLAGS: 476af700 > Not tainted > EAX: 47cfc500 EBX: 0a024d00 ECX: 086c75fc EDX: 080fff88 > ESI: 0839f4bc EDI: 47cfc500 EBP: 0839f4bc DS: c500 ES: cd62 > EXT4-fs (ubda): error count: 1 > EXT4-fs (ubda): initial error at 1398962134: ext4_mb_generate_buddy:7= 56 > EXT4-fs (ubda): last error at 1398962134: ext4_mb_generate_buddy:756 Hmm, there is another bug hidden. /me looks. >=20 > which is a big improvement because before it crashes immediately afte= r few seconds. >=20 > After applying both fixes the test case runs w/o a crash till now. It should work without removing the panics(). Otherwise an attacker could do nasty things. Thanks, //richard