All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ke Liu <1796754@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1796754] Re: ioctl SIOCGIFCONF causes qemu-aarch64-static to crash with "received signal outside vCPU context"
Date: Mon, 08 Oct 2018 21:43:17 -0000	[thread overview]
Message-ID: <153903499788.12323.5168552902265405655.malone@wampee.canonical.com> (raw)
In-Reply-To: 153902784309.8245.8166003544722634075.malonedeb@soybean.canonical.com

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

  reply	other threads:[~2018-10-08 21:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08 19:44 [Qemu-devel] [Bug 1796754] [NEW] ioctl SIOCGIFCONF causes qemu-aarch64-static to crash with "received signal outside vCPU context" Ke Liu
2018-10-08 21:43 ` Ke Liu [this message]
2018-10-09 23:11 ` [Qemu-devel] [Bug 1796754] " Ke Liu
2018-10-23 20:35 ` Alex Bennée
2018-12-03  9:06 ` Kan Li
2019-04-24  5:32 ` Thomas Huth

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=153903499788.12323.5168552902265405655.malone@wampee.canonical.com \
    --to=1796754@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.