[Qemu-commits] [qemu/qemu] dab32b: linux-user: Fix handling of iovec counts

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/qemu/qemu
  Commit: dab32b321f4d510ed5171b12f68bd5aa7a02cffe
      
https://github.com/qemu/qemu/commit/dab32b321f4d510ed5171b12f68bd5aa7a02cffe
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/syscall.c

  Log Message:
  -----------
  linux-user: Fix handling of iovec counts

In the kernel the length of an iovec is generally handled as
an unsigned long, not an integer; fix the parameter to
lock_iovec() accordingly.

Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: 97b079703350ec0f6625788fb380f1fa14d0e2c4
      
https://github.com/qemu/qemu/commit/97b079703350ec0f6625788fb380f1fa14d0e2c4
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/syscall.c

  Log Message:
  -----------
  linux-user: Fix errno for sendrecvmsg with large iovec length

The sendmsg and recvmsg syscalls use a different errno to indicate
an overlarge iovec length from readv and writev. Handle this
special case in do_sendrcvmsg_locked() to avoid getting the
default errno returned by lock_iovec().

Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: 26a6fc96e0ca7522b855c2164bc6098240c286f6
      
https://github.com/qemu/qemu/commit/26a6fc96e0ca7522b855c2164bc6098240c286f6
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/syscall.c

  Log Message:
  -----------
  linux-user: Allow bad msg_name for recvfrom on connected socket

The POSIX standard mandates that for a connected socket recvfrom()
must ignore the msg_name and msg_namelen fields. This is awkward
for QEMU because we will attempt to copy them from guest address
space. Handle this by not immediately returning a TARGET_EFAULT
if the copy failed, but instead passing a known-bad address
to the host kernel, which can then return EFAULT or ignore the
value appropriately.

Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: 6080723102d1ad3b553769834d6a23e3f3d8250f
      
https://github.com/qemu/qemu/commit/6080723102d1ad3b553769834d6a23e3f3d8250f
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/ioctls.h
    M linux-user/syscall_defs.h

  Log Message:
  -----------
  linux-user: Implement FS_IOC_GETFLAGS and FS_IOC_SETFLAGS ioctls

Implement the FS_IOC_GETFLAGS and FS_IOC_SETFLAGS ioctls, as used
by chattr.

Note that the type information encoded in these ioctl numbers
is at odds with the actual type the kernel accesses, as discussed
in http://thread.gmane.org/gmane.linux.file-systems/80164.

Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: 700fa58e4b9100d6bd77df06d2e5d1f457720c4d
      
https://github.com/qemu/qemu/commit/700fa58e4b9100d6bd77df06d2e5d1f457720c4d
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/syscall.c

  Log Message:
  -----------
  linux-user: Use direct syscall for utimensat

The linux utimensat syscall differs in semantics from the
libc function because the syscall combines the features
of utimensat() and futimens(). Rather than trying to
split these apart in order to call the two libc functions
which then call the same underlying syscall, just always
directly make the host syscall. This fixes bugs in some
of the corner cases which should return errors from the
syscall but which we were incorrectly directing to futimens().

This doesn't reduce the set of hosts that our syscall
implementation will work on, because if the direct syscall
fails ENOSYS then the libc functions would also fail ENOSYS.
(The system call has been in the kernel since 2.6.22 anyway.)

Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: 2ba7fae3bd688f5bb6cb08defc731d77e6bd943c
      
https://github.com/qemu/qemu/commit/2ba7fae3bd688f5bb6cb08defc731d77e6bd943c
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/syscall.c
    M linux-user/syscall_defs.h

  Log Message:
  -----------
  linux-user: Check for bad event numbers in epoll_wait

The kernel checks that the maxevents parameter to epoll_wait
is non-negative and not larger than EP_MAX_EVENTS. Add this
check to our implementation, so that:
 * we fail these cases EINVAL rather than EFAULT
 * we don't pass negative or overflowing values to the
   lock_user() size calculation

Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: ce9c139d93db03e464341385976606b7568b768f
      
https://github.com/qemu/qemu/commit/ce9c139d93db03e464341385976606b7568b768f
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/syscall.c

  Log Message:
  -----------
  linux-user: Range check the nfds argument to ppoll syscall

Do an initial range check on the ppoll syscall's nfds argument,
to avoid possible overflow in the calculation of the lock_user()
size argument. The host kernel will later apply the rather lower
limit based on RLIMIT_NOFILE as appropriate.

Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: 0cb581d6bdc5aa808ae1a9789d02657fe531cb39
      
https://github.com/qemu/qemu/commit/0cb581d6bdc5aa808ae1a9789d02657fe531cb39
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/qemu.h
    M linux-user/signal.c
    M linux-user/strace.c

  Log Message:
  -----------
  linux-user: report signals being taken in strace output

Native strace reports when the process being traced takes a signal:
   --- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=0} ---

Report something similar when QEMU is doing its internal strace of
the guest process and is about to deliver it a signal.

Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: 68754b442b756e8cb5f143b00937fb7330a51a81
      
https://github.com/qemu/qemu/commit/68754b442b756e8cb5f143b00937fb7330a51a81
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/elfload.c

  Log Message:
  -----------
  linux-user: Pass missing MAP_ANONYMOUS to target_mmap() call

A target_mmap() call in load_elf_binary() was missing the MAP_ANONYMOUS
flag. (Spotted by Coverity, because target_mmap() will try to use
-1 as the filedescriptor in this case.)

This has never been noticed because the code in question is for
handling ancient SVr4 iBCS2 binaries.

Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: 3211215e741f6e4824ddfc4919428e8d1b82a3c2
      
https://github.com/qemu/qemu/commit/3211215e741f6e4824ddfc4919428e8d1b82a3c2
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/syscall.c

  Log Message:
  -----------
  linux-user: Check lock_user() return value for NULL

lock_user() can return NULL, which typically means the syscall
should fail with EFAULT. Add checks in various places where
Coverity spotted that we were missing them.

Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: f9757b1d9649cb739ecf544c7137c0885281f6e8
      
https://github.com/qemu/qemu/commit/f9757b1d9649cb739ecf544c7137c0885281f6e8
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/syscall.c

  Log Message:
  -----------
  linux-user: Fix incorrect use of host errno in do_ioctl_dm()

do_ioctl_dm() should return target errno values, not host ones;
correct an accidental use of a host errno in an error path.

Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: e5a869ed569a97fa676e9827952629086ec41f4e
      
https://github.com/qemu/qemu/commit/e5a869ed569a97fa676e9827952629086ec41f4e
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/flatload.c

  Log Message:
  -----------
  linux-user: Fix error handling in flatload.c target_pread()

The flatload.c target_pread() function is supposed to return
0 on success or negative host errnos; however it wasn't
checking lock_user() for failure or returning the errno from
the pread() call. Fix these problems (the first of which is
noted by Coverity).

Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: 772034b63e9c0caf6c92e31413f2d8df2ee69c88
      
https://github.com/qemu/qemu/commit/772034b63e9c0caf6c92e31413f2d8df2ee69c88
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/elfload.c

  Log Message:
  -----------
  linux-user: Check dump_write() return in elf_core_dump()

One of the calls to dump_write() in elf_core_dump() was missing
a check for failure (spotted by Coverity). Add the check to
bring it into line with the other calls from this function.

Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: 0ef9ea290ed9319cb788ea40be06dd18b32ba05a
      
https://github.com/qemu/qemu/commit/0ef9ea290ed9319cb788ea40be06dd18b32ba05a
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/elfload.c

  Log Message:
  -----------
  linux-user: Use glib malloc functions in load_symbols()

Switch to using the glib malloc functions in load_symbols();
this deals with a Coverity complaint about possible
integer overflow calculating the allocation size with
'nsyms * sizeof(*syms)'.

Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: ee8e76141b4dd00f8e97fda274876a17f9a46bbe
      
https://github.com/qemu/qemu/commit/ee8e76141b4dd00f8e97fda274876a17f9a46bbe
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/arm/target_syscall.h
    M linux-user/mips/target_syscall.h
    M linux-user/mips64/target_syscall.h
    M linux-user/sh4/target_syscall.h
    M linux-user/sparc/target_syscall.h
    M linux-user/syscall.c

  Log Message:
  -----------
  linux-user: Use correct target SHMLBA in shmat()

The shmat() handling needs to do target-specific handling
of the attach address for shmat():
 * if the SHM_RND flag is passed, the address is rounded
   down to a SHMLBA boundary
 * if SHM_RND is not passed, then the call is failed EINVAL
   if the address is not a multiple of SHMLBA

Since SHMLBA is target-specific, we need to do this
checking and rounding in QEMU and can't leave it up to the
host syscall.

Allow targets to define TARGET_FORCE_SHMLBA and provide
a target_shmlba() function if appropriate, and update
do_shmat() to honour them.

Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: c836112997e19966565cd6eb68e0836c8972720b
      
https://github.com/qemu/qemu/commit/c836112997e19966565cd6eb68e0836c8972720b
  Author: Michael Walle <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/main.c

  Log Message:
  -----------
  linux-user: ppc64: set MSR_CM bit for BookE 2.06 MMU

64 bit user mode doesn't work for the e5500 core because the MSR_CM bit is
not set which enables the 64 bit mode for this MMU model. Memory addresses
are truncated to 32 bit, which results in "Invalid data memory access"
error messages. Fix it by setting the MSR_CM bit for this MMU model.

Signed-off-by: Michael Walle <address@hidden>
Reviewed-by: Alexander Graf <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: 8bd3773cce1885c46e5cf09a72b9138ccba5fbf2
      
https://github.com/qemu/qemu/commit/8bd3773cce1885c46e5cf09a72b9138ccba5fbf2
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/signal.c

  Log Message:
  -----------
  linux-user: Recheck for pending synchronous signals too

In process_pending_signals() we restart the scan of possible
pending signals after calling handle_pending_signal() in
case some other signal has been generated. This rescan
should also include a check for a new synchronous signal
since those are in fact the only kind of new signal that
the signal frame setup process might produce.

Reviewed-by: Richard Henderson <address@hidden>
Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: 9d2803f720d5b71937c0f564bb2c16d8f5e18c8c
      
https://github.com/qemu/qemu/commit/9d2803f720d5b71937c0f564bb2c16d8f5e18c8c
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/main.c
    M linux-user/qemu.h
    M linux-user/signal.c
    M linux-user/syscall.c

  Log Message:
  -----------
  linux-user: Pass si_type information to queue_signal() explicitly

Instead of assuming in queue_signal() that all callers are passing
a siginfo structure which uses the _sifields._sigfault part of the
union (and thus a si_type of QEMU_SI_FAULT), make callers pass
the si_type they require in as an argument.

[RV adjusted to apply]
Reviewed-by: Richard Henderson <address@hidden>
Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: 09391669975a0e2882c181982d4ddee35a0080bb
      
https://github.com/qemu/qemu/commit/09391669975a0e2882c181982d4ddee35a0080bb
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/signal.c

  Log Message:
  -----------
  linux-user: SIGSEGV on signal entry need not be fatal

A failed write to memory trying to set up the signal frame
should trigger a SIGSEGV, but this need not be fatal: the
guest has a chance to catch it. Implement this via a force_sigsegv()
function with the same behaviour as the kernel function of that
name: make sure that we don't try to re-take a failed SIGSEGV,
and force a synchronous signal.

Reviewed-by: Richard Henderson <address@hidden>
Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: 28298c912e2c379f2b7767b351beeb77f001f27f
      
https://github.com/qemu/qemu/commit/28298c912e2c379f2b7767b351beeb77f001f27f
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/signal.c

  Log Message:
  -----------
  linux-user: ARM: Give SIGSEGV if signal frame setup fails

The 32-bit ARM signal frame setup code was just bailing out
on error returns from lock_user_struct calls, without
generating the SIGSEGV that should happen here. Wire up
error return codes to call force_sigsegv().

Reviewed-by: Richard Henderson <address@hidden>
Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: c599d4d6d6e9bfdb64e54c33a22cb26e3496b96d
      
https://github.com/qemu/qemu/commit/c599d4d6d6e9bfdb64e54c33a22cb26e3496b96d
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/signal.c

  Log Message:
  -----------
  linux-user: SIGSEGV from sigreturn need not be fatal

If the sigreturn syscall fails to read memory then this causes a
SIGSEGV, but this is not necessarily a fatal signal -- the guest
process can catch it.

We don't implement this correctly because the behaviour of QEMU's
force_sig() function has drifted away from the kernel function of the
same name -- ours now does "always do a guest core dump and abort
execution", whereas the kernel version simply forces the guest to
take a signal, which may or may not eventually cause a core dump.

Rename our force_sig() to dump_core_and_abort(), and provide a
force_sig() which acts more like the kernel version as the sigreturn
implementations expect it to.  Since force_sig() now returns, we must
update all the callsites to return -TARGET_QEMU_ESIGRETURN so that
the main loop doesn't change the guest registers before the signal
handler is invoked.

Reviewed-by: Richard Henderson <address@hidden>
Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: c4b3574402053a88612eab3b66a53825a00145a2
      
https://github.com/qemu/qemu/commit/c4b3574402053a88612eab3b66a53825a00145a2
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/signal.c

  Log Message:
  -----------
  linux-user: Implement force_sigsegv() via force_sig()

Now that we have a force_sig() with the semantics we need,
we can implement force_sigsegv() to call it rather than
open-coding the call to queue_signal().

Reviewed-by: Richard Henderson <address@hidden>
Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: 7cfbd386b92e93fbfae033b9ac89a20d1fe72573
      
https://github.com/qemu/qemu/commit/7cfbd386b92e93fbfae033b9ac89a20d1fe72573
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/syscall.c

  Log Message:
  -----------
  linux-user: Remove unnecessary nptl_flags variable from do_fork()

The 'nptl_flags' variable in do_fork() is set to a copy of
'flags', and then the CLONE_NPTL_FLAGS are cleared out of 'flags'.
However the only effect of this is that the later check on
"if (flags & CLONE_PARENT_SETTID)" is never true. Since we
will already have done the setting of parent_tidptr in clone_func()
in the child thread, we don't need to do it again.

Delete the dead if() and the clearing of CLONE_NPTL_FLAGS from
'flags', and then use 'flags' where we were previously using
'nptl_flags', so we can delete the unnecessary variable.

Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: 5ea2fc84da1bffce749c9d0848f5336def2818bb
      
https://github.com/qemu/qemu/commit/5ea2fc84da1bffce749c9d0848f5336def2818bb
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/syscall.c

  Log Message:
  -----------
  linux-user: Sanity check clone flags

We currently make no checks on the flags passed to the clone syscall,
which means we will not fail clone attempts which ask for features
that we can't implement. Add sanity checking of the flags to clone
(which we were already doing in the "this is a fork" path, but not
for the "this is a new thread" path), tidy up the checking in
the fork path to match it, and check that the fork case isn't trying
to specify a custom termination signal.

This is helpful in causing some LTP test cases to fail cleanly
rather than behaving bizarrely when we let the clone succeed
but didn't provide the semantics requested by the flags.

Signed-off-by: Peter Maydell <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: 45eafb4d32ced9ff1dcb3800c89f8beaf47b61cc
      
https://github.com/qemu/qemu/commit/45eafb4d32ced9ff1dcb3800c89f8beaf47b61cc
  Author: Timothy E Baldwin <address@hidden>
  Date:   2016-09-21 (Wed, 21 Sep 2016)

  Changed paths:
    M linux-user/signal.c

  Log Message:
  -----------
  linux-user: Fix incorrect offset of tuc_stack in ARM do_sigframe_return_v2

struct target_ucontext_v2 is not at the begining of the signal frame,
therefore do_sigaltstack was being passed bogus arguments.

As the offset depends on the type of signal frame fixed by passing in the
beginning of the context from do_sigreturn_v2 and do_rt_sigreturn_v2.

Suggested-by: Peter Maydell <address@hidden>
Reviewed-by: Peter Maydell <address@hidden>
Signed-off-by: Timothy Edward Baldwin <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: 5457dc9e37fe0a29989bd64306c63941074864ce
      
https://github.com/qemu/qemu/commit/5457dc9e37fe0a29989bd64306c63941074864ce
  Author: Laurent Vivier <address@hidden>
  Date:   2016-09-22 (Thu, 22 Sep 2016)

  Changed paths:
    M linux-user/arm/target_syscall.h
    M linux-user/i386/target_syscall.h
    M linux-user/m68k/target_syscall.h
    M linux-user/microblaze/target_syscall.h
    M linux-user/openrisc/syscall_nr.h
    M linux-user/ppc/target_syscall.h
    M linux-user/sh4/syscall_nr.h
    M linux-user/syscall.c
    M linux-user/tilegx/syscall_nr.h

  Log Message:
  -----------
  linux-user: fix TARGET_NR_select

TARGET_NR_select can have three different implementations:

  1- to always return -ENOSYS

     microblaze, ppc, ppc64

     -> TARGET_WANT_NI_OLD_SELECT

  2- to take parameters from a structure pointed by arg1
    (kernel sys_old_select)

     i386, arm, m68k

     -> TARGET_WANT_OLD_SYS_SELECT

  3- to take parameters from arg[1-5]
     (kernel sys_select)

     x86_64, alpha, s390x,
     cris, sparc, sparc64

Some (new) architectures don't define NR_select,

  4- but only NR__newselect with sys_select:

      mips, mips64, sh

  5- don't define NR__newselect, and use pselect6 syscall:

      aarch64, openrisc, tilegx, unicore32

Reported-by: Timothy Pearson <address@hidden>
Reported-by: Allan Wirth <address@hidden>
Suggested-by: Peter Maydell <address@hidden>
Reviewed-by: Peter Maydell <address@hidden>
Signed-off-by: Laurent Vivier <address@hidden>
Signed-off-by: Riku Voipio <address@hidden>


  Commit: 430da7a81d356e368ccd88dcca60f38da9aa5b9a
      
https://github.com/qemu/qemu/commit/430da7a81d356e368ccd88dcca60f38da9aa5b9a
  Author: Peter Maydell <address@hidden>
  Date:   2016-09-22 (Thu, 22 Sep 2016)

  Changed paths:
    M linux-user/arm/target_syscall.h
    M linux-user/elfload.c
    M linux-user/flatload.c
    M linux-user/i386/target_syscall.h
    M linux-user/ioctls.h
    M linux-user/m68k/target_syscall.h
    M linux-user/main.c
    M linux-user/microblaze/target_syscall.h
    M linux-user/mips/target_syscall.h
    M linux-user/mips64/target_syscall.h
    M linux-user/openrisc/syscall_nr.h
    M linux-user/ppc/target_syscall.h
    M linux-user/qemu.h
    M linux-user/sh4/syscall_nr.h
    M linux-user/sh4/target_syscall.h
    M linux-user/signal.c
    M linux-user/sparc/target_syscall.h
    M linux-user/strace.c
    M linux-user/syscall.c
    M linux-user/syscall_defs.h
    M linux-user/tilegx/syscall_nr.h

  Log Message:
  -----------
  Merge remote-tracking branch 'remotes/riku/tags/pull-linux-user-20160915' 
into staging

linux-user changes since 2.7 release

# gpg: Signature made Thu 22 Sep 2016 13:09:17 BST
# gpg:                using RSA key 0xB44890DEDE3C9BC0
# gpg: Good signature from "Riku Voipio <address@hidden>"
# gpg:                 aka "Riku Voipio <address@hidden>"
# Primary key fingerprint: FF82 03C8 C391 98AE 0581  41EF B448 90DE DE3C 9BC0

* remotes/riku/tags/pull-linux-user-20160915: (26 commits)
  linux-user: fix TARGET_NR_select
  linux-user: Fix incorrect offset of tuc_stack in ARM do_sigframe_return_v2
  linux-user: Sanity check clone flags
  linux-user: Remove unnecessary nptl_flags variable from do_fork()
  linux-user: Implement force_sigsegv() via force_sig()
  linux-user: SIGSEGV from sigreturn need not be fatal
  linux-user: ARM: Give SIGSEGV if signal frame setup fails
  linux-user: SIGSEGV on signal entry need not be fatal
  linux-user: Pass si_type information to queue_signal() explicitly
  linux-user: Recheck for pending synchronous signals too
  linux-user: ppc64: set MSR_CM bit for BookE 2.06 MMU
  linux-user: Use correct target SHMLBA in shmat()
  linux-user: Use glib malloc functions in load_symbols()
  linux-user: Check dump_write() return in elf_core_dump()
  linux-user: Fix error handling in flatload.c target_pread()
  linux-user: Fix incorrect use of host errno in do_ioctl_dm()
  linux-user: Check lock_user() return value for NULL
  linux-user: Pass missing MAP_ANONYMOUS to target_mmap() call
  linux-user: report signals being taken in strace output
  linux-user: Range check the nfds argument to ppoll syscall
  ...

Signed-off-by: Peter Maydell <address@hidden>


Compare: https://github.com/qemu/qemu/compare/3648100e2af8...430da7a81d35