trinity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: trinity@vger.kernel.org
Cc: UML devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: trinity commit 23dc478aba  breaks syscall "mremap" at a 32 bit user mode linux
Date: Wed, 30 Apr 2014 20:19:02 +0200	[thread overview]
Message-ID: <53613E96.2030006@gmx.de> (raw)

-or- it uncovers a bug in kernel v3.15-rc3 for UML:



commit 23dc478aba4134db51584d19e4783ec87ce87b88
Author: Dave Jones <davej@redhat.com>
Date:   Tue Apr 29 16:42:45 2014 -0400

    non-biarch arches aren't necessarily 32-bit.

diff --git a/children/random-syscalls.c b/children/random-syscalls.c
index 82e49f5..1d7e7ce 100644
--- a/children/random-syscalls.c
+++ b/children/random-syscalls.c
@@ -32,7 +32,6 @@ static bool choose_syscall_table(void)

        if (biarch == FALSE) {
                active_syscalls = shm->active_syscalls;
-               do32 = TRUE;
        } else {

                /* First, check that we have syscalls enabled in either table. */




I do get :


Kernel panic - not syncing: do_syscall_stub : PTRACE_SETREGS failed, errno = 3

CPU: 0 PID: 1303 Comm: trinity-c0 Not tainted 3.15.0-rc3 #1
Stack:
 085a4f54 085a4f54 4841fc48 00000004 086c8547 00002b58 00000003 00000011
 4841fc58 084eae75 00000000 00000000 4841fc80 084e72e0 085b08e8 08700960
 085ad7b4 4841fc90 00000000 00002b58 00000003 00000011 4841fcb4 080734c5
Call Trace:
 [<080734c5>] ? run_syscall_stub+0x125/0x2c0
 [<084eae75>] dump_stack+0x26/0x28
 [<084e72e0>] panic+0x7a/0x194
 [<080734c5>] run_syscall_stub+0x125/0x2c0
 [<08073b15>] unmap+0xf5/0x110
 [<08061047>] do_ops+0xb7/0x160
 [<080615f8>] fix_range_common+0x448/0x480
 [<080e50f4>] ? vma_interval_tree_insert+0x74/0x80
 [<0806193e>] flush_tlb_range+0x3e/0x40
 [<080f045e>] move_page_tables+0x24e/0x280
 [<080f0577>] move_vma+0xe7/0x230
 [<080eda20>] ? get_unmapped_area+0xa0/0xc0
 [<080f08b8>] SyS_mremap+0x1f8/0x4c0
 [<08062ab4>] handle_syscall+0x64/0x80
 [<0849d4f1>] ? ptrace+0x31/0x80
 [<080797a2>] ? get_fp_registers+0x22/0x40
 [<08074815>] userspace+0x475/0x5f0
 [<0849d4f1>] ? ptrace+0x31/0x80
 [<08079d06>] ? os_set_thread_area+0x26/0x40
 [<08078cd0>] ? do_set_thread_area+0x20/0x50
 [<08078e48>] ? arch_switch_tls+0xb8/0x100
 [<0805f770>] fork_handler+0x60/0x70

/home/tfoerste/workspace/bin/start_uml.sh: line 110:  9558 Aborted                 (core dumped) $LINUX earlyprintk ubda=$ROOTFS ubdb=$SWAP eth0=$NET mem=$MEM $TTY umid=uml_$NAME rootfstype=ext4 "$ARGS"


-- 
Toralf

             reply	other threads:[~2014-04-30 18:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30 18:19 Toralf Förster [this message]
2014-05-01  9:22 ` [uml-devel] trinity commit 23dc478aba breaks syscall "mremap" at a 32 bit user mode linux Richard Weinberger
2014-05-01 10:29   ` Toralf Förster
2014-05-01 12:33     ` Richard Weinberger
2014-05-01 15:15       ` Toralf Förster
2014-05-01 20:57         ` Richard Weinberger
2014-05-01 21:34           ` Toralf Förster
2014-05-02  7:21             ` Richard Weinberger
2014-05-02  7:46             ` Richard Weinberger
2014-05-02 14:07               ` Toralf Förster
2014-05-02 14:14                 ` Richard Weinberger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53613E96.2030006@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=trinity@vger.kernel.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).