[Qemu-devel] [Bug 1796754] Re: ioctl SIOCGIFCONF causes qemu-aarch64-static to crash with "received signal outside vCPU context"

[Ke Liu]

I was hit by this issue when I tried to run some Java program. And it
turns out jdk sets the buf to NULL:
http://hg.openjdk.java.net/jdk7/jdk7/jdk/file/887e525597f8/src/solaris/native/java/net/NetworkInterface.c#l1042

Setting to NULL is valid according to http://man7.org/linux/man-
pages/man7/netdevice.7.html

But qemu doesn’t handle the case:
https://github.com/qemu/qemu/blob/aa8e26de9617756febcbf794dda965df307fdaaa
/linux-user/syscall.c#L4105

I guess qemu developers didn’t handle the case because the Linux kernel
changed and they were based on behavior of old version:
https://linux.die.net/man/7/netdevice

Please add the support for it otherwise a wide range of network related
Java programs won’t run.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1796754

Title:
  ioctl SIOCGIFCONF causes qemu-aarch64-static to crash with "received
  signal outside vCPU context"

Status in QEMU:
  New

Bug description:
  To reproduce it, compile the attached crash.c under aarch64 to a.out and 
execute on x86_64
  qemu-aarch64-static ./a.out

  It will print the following and crash:

  socket=3
  qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x60038cd6
  qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6000157a

  The version of qemu-aarch64-static is

  qemu-aarch64 version 3.0.0 (qemu-3.0.0-1.fc29)
  Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers

  But it did also happen in previous versions so it is not a regression
  but a bug existed ever since.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1796754/+subscriptions