qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 1796754] [NEW] ioctl SIOCGIFCONF causes qemu-aarch64-s


From: Ke Liu
Subject: [Qemu-devel] [Bug 1796754] [NEW] ioctl SIOCGIFCONF causes qemu-aarch64-static to crash with "received signal outside vCPU context"
Date: Mon, 08 Oct 2018 19:44:02 -0000

Public bug reported:

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.

** Affects: qemu
     Importance: Undecided
         Status: New


** Tags: aarch64 arm linux-user qemu

** Attachment added: "crash.c"
   https://bugs.launchpad.net/bugs/1796754/+attachment/5198861/+files/crash.c

** Tags added: aarch64

** Tags added: linux-user qemu

** Tags added: arm

-- 
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 via email to

[Prev in Thread] Current Thread [Next in Thread]