All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Berrange <1815889@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()
Date: Tue, 02 Apr 2019 17:38:08 -0000	[thread overview]
Message-ID: <155422668873.21090.14194628601898762658.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 155014036044.634.15252078016929169795.malonedeb@gac.canonical.com

FYI the QEMU change merged in the following pull request changed to
return an EPERM errno for the thread affinity syscalls:

commit 12f067cc14b90aef60b2b7d03e1df74cc50a0459
Merge: 84bdc58c06 035121d23a
Author: Peter Maydell <peter.maydell@linaro.org>
Date:   Thu Mar 28 12:04:52 2019 +0000

    Merge remote-tracking branch 'remotes/otubo/tags/pull-seccomp-20190327' into staging
    
    pull-seccomp-20190327
    
    # gpg: Signature made Wed 27 Mar 2019 12:12:39 GMT
    # gpg:                using RSA key DF32E7C0F0FFF9A2
    # gpg: Good signature from "Eduardo Otubo (Senior Software Engineer) <otubo@redhat.com>" [full]
    # Primary key fingerprint: D67E 1B50 9374 86B4 0723  DBAB DF32 E7C0 F0FF F9A2
    
    * remotes/otubo/tags/pull-seccomp-20190327:
      seccomp: report more useful errors from seccomp
      seccomp: don't kill process for resource control syscalls
    
    Signed-off-by: Peter Maydell <peter.maydell@linaro.org>

IOW, mesa's usage of this syscalls will still be blocked, but it will no
longer kill the process.

** Changed in: qemu
       Status: New => Fix Committed

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

Title:
  qemu-system-x86_64 crashed with signal 31 in
  __pthread_setaffinity_new()

Status in Mesa:
  Confirmed
Status in QEMU:
  Fix Committed
Status in mesa package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Triaged
Status in mesa source package in Disco:
  Fix Released

Bug description:
  Unable to launch Default Fedora 29 images in gnome-boxes

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  Date: Thu Feb 14 11:00:45 2019
  ExecutablePath: /usr/bin/qemu-system-x86_64
  KvmCmdLine: COMMAND         STAT  EUID  RUID   PID  PPID %CPU COMMAND
  MachineType: Dell Inc. Precision T3610
  ProcEnviron: PATH=(custom, user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1
  Signal: 31
  SourcePackage: qemu
  StacktraceTop:
   __pthread_setaffinity_new (th=<optimized out>, cpusetsize=128, cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   start_thread (arg=<optimized out>) at pthread_create.c:486
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
  Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()
  UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  dmi.bios.date: 11/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 09M8Y8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T3610
  dmi.product.sku: 05D2
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

  parent reply	other threads:[~2019-04-02 17:50 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <155014036044.634.15252078016929169795.malonedeb@gac.canonical.com>
2019-02-27  9:56 ` [Qemu-devel] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() Christian Ehrhardt 
2019-02-27 10:01 ` Christian Ehrhardt 
2019-02-27 10:38 ` Daniel Berrange
2019-02-27 11:07 ` elmarco
2019-02-27 11:32 ` Daniel Berrange
2019-02-27 11:50 ` Daniel Berrange
2019-02-27 13:55 ` elmarco
2019-02-28 10:04 ` Christian Ehrhardt 
2019-02-28 10:08 ` Christian Ehrhardt 
2019-02-28 10:39 ` Will Cooke
2019-02-28 15:09 ` Bug Watch Updater
2019-03-02 11:36 ` [Qemu-devel] [Bug 1815889] Ahzo
2019-03-04  9:03 ` [Qemu-devel] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() Timo Aaltonen
2019-03-04  9:32 ` Christian Ehrhardt 
2019-03-04  9:40 ` Timo Aaltonen
2019-03-04 16:13 ` Christian Ehrhardt 
2019-03-04 16:55 ` Timo Aaltonen
2019-03-04 17:15 ` Christian Ehrhardt 
2019-03-06 18:17 ` [Qemu-devel] [Bug 1815889] Baker-dylan-c
2019-03-11 17:04 ` Baker-dylan-c
2019-04-02 13:03 ` Marek Olšák
2019-04-02 17:38 ` Daniel Berrange [this message]
2019-04-03 12:09 ` [Qemu-devel] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() Christian Ehrhardt 
2019-04-13 13:50 ` [Qemu-devel] [Bug 1815889] Ahzo
2019-04-14  5:30 ` [Qemu-devel] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() Bug Watch Updater
2019-04-24  6:05 ` Thomas Huth
2019-05-07 14:04 ` Sebastien Bacher
2019-05-07 14:28 ` Sebastien Bacher
2019-10-21  9:52 ` Timo Aaltonen
2019-10-21 10:56 ` Timo Aaltonen
2019-10-28 12:49 ` Timo Aaltonen
2019-11-25 19:37 ` Launchpad Bug Tracker

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=155422668873.21090.14194628601898762658.malone@chaenomeles.canonical.com \
    --to=1815889@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.