qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] [Bug 1815911] [NEW] aptitude crashes qemu-m68k with handle_cpu_signal received signal outside vCPU context
@ 2019-02-14 13:53 John Paul Adrian Glaubitz
  2019-02-15 12:47 ` [Qemu-devel] [Bug 1815911] " Laurent Vivier
                   ` (4 more replies)
  0 siblings, 5 replies; 7+ messages in thread
From: John Paul Adrian Glaubitz @ 2019-02-14 13:53 UTC (permalink / raw)
  To: qemu-devel

Public bug reported:

When building a package with sbuild on Debian, sbuild can use aptitude
to resolve dependencies.

Recently, some changes introduced to aptitude or related packages cause
qemu to crash:

(sid-m68k-sbuild)root@nofan:/# aptitude -y --without-recommends -o Dpkg::Options::=--force-confold -o Aptitude::CmdLine::Ignore-Trust-Violations=false -o Aptitude::ProblemResolver::StepScore=100 -o Aptitude::ProblemResolver::SolutionCost="safety, priority, non-default-versions" -o Aptitude::ProblemResolver::Hints::KeepDummy="reject sbuild-build-depends-core-dummy :UNINST" -o Aptitude::ProblemResolver::Keep-All-Level=55000 -o Aptitude::ProblemResolver::Remove-Essential-Level=maximum install vim
Warning: Invalid locale (please review locale settings, this might lead to problems later):
  locale::facet::_S_create_c_locale name not valid
The following NEW packages will be installed:
  libgpm2{a} vim vim-common{a} vim-runtime{a} xxd{a} 
0 packages upgraded, 5 newly installed, 0 to remove and 1 not upgraded.
Need to get 7225 kB/7260 kB of archives. After unpacking 33.5 MB will be used.
qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6019d1bf
qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x601b64ab
Segmentation fault
(sid-m68k-sbuild)root@nofan:/#

The crash does not reproduce on real hardware running Debian unstable.

** Affects: qemu
     Importance: Undecided
         Status: New

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

Title:
  aptitude crashes qemu-m68k with handle_cpu_signal received signal
  outside vCPU context

Status in QEMU:
  New

Bug description:
  When building a package with sbuild on Debian, sbuild can use aptitude
  to resolve dependencies.

  Recently, some changes introduced to aptitude or related packages
  cause qemu to crash:

  (sid-m68k-sbuild)root@nofan:/# aptitude -y --without-recommends -o Dpkg::Options::=--force-confold -o Aptitude::CmdLine::Ignore-Trust-Violations=false -o Aptitude::ProblemResolver::StepScore=100 -o Aptitude::ProblemResolver::SolutionCost="safety, priority, non-default-versions" -o Aptitude::ProblemResolver::Hints::KeepDummy="reject sbuild-build-depends-core-dummy :UNINST" -o Aptitude::ProblemResolver::Keep-All-Level=55000 -o Aptitude::ProblemResolver::Remove-Essential-Level=maximum install vim
  Warning: Invalid locale (please review locale settings, this might lead to problems later):
    locale::facet::_S_create_c_locale name not valid
  The following NEW packages will be installed:
    libgpm2{a} vim vim-common{a} vim-runtime{a} xxd{a} 
  0 packages upgraded, 5 newly installed, 0 to remove and 1 not upgraded.
  Need to get 7225 kB/7260 kB of archives. After unpacking 33.5 MB will be used.
  qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6019d1bf
  qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x601b64ab
  Segmentation fault
  (sid-m68k-sbuild)root@nofan:/#

  The crash does not reproduce on real hardware running Debian unstable.

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Qemu-devel] [Bug 1815911] Re: aptitude crashes qemu-m68k with handle_cpu_signal received signal outside vCPU context
  2019-02-14 13:53 [Qemu-devel] [Bug 1815911] [NEW] aptitude crashes qemu-m68k with handle_cpu_signal received signal outside vCPU context John Paul Adrian Glaubitz
@ 2019-02-15 12:47 ` Laurent Vivier
  2019-02-16 17:11   ` John Paul Adrian Glaubitz
  2020-08-10 15:20 ` Steve Dodd
                   ` (3 subsequent siblings)
  4 siblings, 1 reply; 7+ messages in thread
From: Laurent Vivier @ 2019-02-15 12:47 UTC (permalink / raw)
  To: qemu-devel

It seems it crashes during futex syscall:

...
[pid     4] getpid()                    = 4
[pid     4] tgkill(4, 24, SIGRT_1)      = 0
[pid    24] <... futex resumed> )       = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
[pid    24] --- SIGRT_1 {si_signo=SIGRT_1, si_code=SI_TKILL, si_pid=4, si_uid=0} ---
[pid     4] futex(0x7f77abb4f610, FUTEX_WAIT_PRIVATE, 16777216, NULL <unfinished ...>
[pid    24] getpid()                    = 4
[pid    24] --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x10} ---
...

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

Title:
  aptitude crashes qemu-m68k with handle_cpu_signal received signal
  outside vCPU context

Status in QEMU:
  New

Bug description:
  When building a package with sbuild on Debian, sbuild can use aptitude
  to resolve dependencies.

  Recently, some changes introduced to aptitude or related packages
  cause qemu to crash:

  (sid-m68k-sbuild)root@nofan:/# aptitude -y --without-recommends -o Dpkg::Options::=--force-confold -o Aptitude::CmdLine::Ignore-Trust-Violations=false -o Aptitude::ProblemResolver::StepScore=100 -o Aptitude::ProblemResolver::SolutionCost="safety, priority, non-default-versions" -o Aptitude::ProblemResolver::Hints::KeepDummy="reject sbuild-build-depends-core-dummy :UNINST" -o Aptitude::ProblemResolver::Keep-All-Level=55000 -o Aptitude::ProblemResolver::Remove-Essential-Level=maximum install vim
  Warning: Invalid locale (please review locale settings, this might lead to problems later):
    locale::facet::_S_create_c_locale name not valid
  The following NEW packages will be installed:
    libgpm2{a} vim vim-common{a} vim-runtime{a} xxd{a} 
  0 packages upgraded, 5 newly installed, 0 to remove and 1 not upgraded.
  Need to get 7225 kB/7260 kB of archives. After unpacking 33.5 MB will be used.
  qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6019d1bf
  qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x601b64ab
  Segmentation fault
  (sid-m68k-sbuild)root@nofan:/#

  The crash does not reproduce on real hardware running Debian unstable.

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [Qemu-devel] [Bug 1815911] Re: aptitude crashes qemu-m68k with handle_cpu_signal received signal outside vCPU context
  2019-02-15 12:47 ` [Qemu-devel] [Bug 1815911] " Laurent Vivier
@ 2019-02-16 17:11   ` John Paul Adrian Glaubitz
  0 siblings, 0 replies; 7+ messages in thread
From: John Paul Adrian Glaubitz @ 2019-02-16 17:11 UTC (permalink / raw)
  To: qemu-devel

On 2/15/19 1:47 PM, Laurent Vivier wrote:
> It seems it crashes during futex syscall:
> 
> ...
> [pid     4] getpid()                    = 4
> [pid     4] tgkill(4, 24, SIGRT_1)      = 0
> [pid    24] <... futex resumed> )       = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
> [pid    24] --- SIGRT_1 {si_signo=SIGRT_1, si_code=SI_TKILL, si_pid=4, si_uid=0} ---
> [pid     4] futex(0x7f77abb4f610, FUTEX_WAIT_PRIVATE, 16777216, NULL <unfinished ...>
> [pid    24] getpid()                    = 4
> [pid    24] --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x10} ---
> ...

The crash also reproduces with qemu-sh4, so it's not specific to m68k.

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

Title:
  aptitude crashes qemu-m68k with handle_cpu_signal received signal
  outside vCPU context

Status in QEMU:
  New

Bug description:
  When building a package with sbuild on Debian, sbuild can use aptitude
  to resolve dependencies.

  Recently, some changes introduced to aptitude or related packages
  cause qemu to crash:

  (sid-m68k-sbuild)root@nofan:/# aptitude -y --without-recommends -o Dpkg::Options::=--force-confold -o Aptitude::CmdLine::Ignore-Trust-Violations=false -o Aptitude::ProblemResolver::StepScore=100 -o Aptitude::ProblemResolver::SolutionCost="safety, priority, non-default-versions" -o Aptitude::ProblemResolver::Hints::KeepDummy="reject sbuild-build-depends-core-dummy :UNINST" -o Aptitude::ProblemResolver::Keep-All-Level=55000 -o Aptitude::ProblemResolver::Remove-Essential-Level=maximum install vim
  Warning: Invalid locale (please review locale settings, this might lead to problems later):
    locale::facet::_S_create_c_locale name not valid
  The following NEW packages will be installed:
    libgpm2{a} vim vim-common{a} vim-runtime{a} xxd{a} 
  0 packages upgraded, 5 newly installed, 0 to remove and 1 not upgraded.
  Need to get 7225 kB/7260 kB of archives. After unpacking 33.5 MB will be used.
  qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6019d1bf
  qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x601b64ab
  Segmentation fault
  (sid-m68k-sbuild)root@nofan:/#

  The crash does not reproduce on real hardware running Debian unstable.

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Bug 1815911] Re: aptitude crashes qemu-m68k with handle_cpu_signal received signal outside vCPU context
  2019-02-14 13:53 [Qemu-devel] [Bug 1815911] [NEW] aptitude crashes qemu-m68k with handle_cpu_signal received signal outside vCPU context John Paul Adrian Glaubitz
  2019-02-15 12:47 ` [Qemu-devel] [Bug 1815911] " Laurent Vivier
@ 2020-08-10 15:20 ` Steve Dodd
  2020-08-12  6:30 ` Thomas Huth
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 7+ messages in thread
From: Steve Dodd @ 2020-08-10 15:20 UTC (permalink / raw)
  To: qemu-devel

I think this is probably a duplicate of bug #1594394, in which case it
seems to be fixed in 5.0.0+.

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

Title:
  aptitude crashes qemu-m68k with handle_cpu_signal received signal
  outside vCPU context

Status in QEMU:
  New

Bug description:
  When building a package with sbuild on Debian, sbuild can use aptitude
  to resolve dependencies.

  Recently, some changes introduced to aptitude or related packages
  cause qemu to crash:

  (sid-m68k-sbuild)root@nofan:/# aptitude -y --without-recommends -o Dpkg::Options::=--force-confold -o Aptitude::CmdLine::Ignore-Trust-Violations=false -o Aptitude::ProblemResolver::StepScore=100 -o Aptitude::ProblemResolver::SolutionCost="safety, priority, non-default-versions" -o Aptitude::ProblemResolver::Hints::KeepDummy="reject sbuild-build-depends-core-dummy :UNINST" -o Aptitude::ProblemResolver::Keep-All-Level=55000 -o Aptitude::ProblemResolver::Remove-Essential-Level=maximum install vim
  Warning: Invalid locale (please review locale settings, this might lead to problems later):
    locale::facet::_S_create_c_locale name not valid
  The following NEW packages will be installed:
    libgpm2{a} vim vim-common{a} vim-runtime{a} xxd{a} 
  0 packages upgraded, 5 newly installed, 0 to remove and 1 not upgraded.
  Need to get 7225 kB/7260 kB of archives. After unpacking 33.5 MB will be used.
  qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6019d1bf
  qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x601b64ab
  Segmentation fault
  (sid-m68k-sbuild)root@nofan:/#

  The crash does not reproduce on real hardware running Debian unstable.

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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Bug 1815911] Re: aptitude crashes qemu-m68k with handle_cpu_signal received signal outside vCPU context
  2019-02-14 13:53 [Qemu-devel] [Bug 1815911] [NEW] aptitude crashes qemu-m68k with handle_cpu_signal received signal outside vCPU context John Paul Adrian Glaubitz
  2019-02-15 12:47 ` [Qemu-devel] [Bug 1815911] " Laurent Vivier
  2020-08-10 15:20 ` Steve Dodd
@ 2020-08-12  6:30 ` Thomas Huth
  2020-08-12  6:44 ` John Paul Adrian Glaubitz
  2020-08-13 19:13 ` Thomas Huth
  4 siblings, 0 replies; 7+ messages in thread
From: Thomas Huth @ 2020-08-12  6:30 UTC (permalink / raw)
  To: qemu-devel

John, can you still reproduce it with the latest version of QEMU?

** Changed in: qemu
       Status: New => Incomplete

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

Title:
  aptitude crashes qemu-m68k with handle_cpu_signal received signal
  outside vCPU context

Status in QEMU:
  Incomplete

Bug description:
  When building a package with sbuild on Debian, sbuild can use aptitude
  to resolve dependencies.

  Recently, some changes introduced to aptitude or related packages
  cause qemu to crash:

  (sid-m68k-sbuild)root@nofan:/# aptitude -y --without-recommends -o Dpkg::Options::=--force-confold -o Aptitude::CmdLine::Ignore-Trust-Violations=false -o Aptitude::ProblemResolver::StepScore=100 -o Aptitude::ProblemResolver::SolutionCost="safety, priority, non-default-versions" -o Aptitude::ProblemResolver::Hints::KeepDummy="reject sbuild-build-depends-core-dummy :UNINST" -o Aptitude::ProblemResolver::Keep-All-Level=55000 -o Aptitude::ProblemResolver::Remove-Essential-Level=maximum install vim
  Warning: Invalid locale (please review locale settings, this might lead to problems later):
    locale::facet::_S_create_c_locale name not valid
  The following NEW packages will be installed:
    libgpm2{a} vim vim-common{a} vim-runtime{a} xxd{a} 
  0 packages upgraded, 5 newly installed, 0 to remove and 1 not upgraded.
  Need to get 7225 kB/7260 kB of archives. After unpacking 33.5 MB will be used.
  qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6019d1bf
  qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x601b64ab
  Segmentation fault
  (sid-m68k-sbuild)root@nofan:/#

  The crash does not reproduce on real hardware running Debian unstable.

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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Bug 1815911] Re: aptitude crashes qemu-m68k with handle_cpu_signal received signal outside vCPU context
  2019-02-14 13:53 [Qemu-devel] [Bug 1815911] [NEW] aptitude crashes qemu-m68k with handle_cpu_signal received signal outside vCPU context John Paul Adrian Glaubitz
                   ` (2 preceding siblings ...)
  2020-08-12  6:30 ` Thomas Huth
@ 2020-08-12  6:44 ` John Paul Adrian Glaubitz
  2020-08-13 19:13 ` Thomas Huth
  4 siblings, 0 replies; 7+ messages in thread
From: John Paul Adrian Glaubitz @ 2020-08-12  6:44 UTC (permalink / raw)
  To: qemu-devel

Just verified it with a very recently compiled version of QEMU from git
master and, indeed, the bug seems to be fixed as I can no longer
reproduce the crash. The command executes correctly.

I guess it's safe to mark this as fixed.

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

Title:
  aptitude crashes qemu-m68k with handle_cpu_signal received signal
  outside vCPU context

Status in QEMU:
  Incomplete

Bug description:
  When building a package with sbuild on Debian, sbuild can use aptitude
  to resolve dependencies.

  Recently, some changes introduced to aptitude or related packages
  cause qemu to crash:

  (sid-m68k-sbuild)root@nofan:/# aptitude -y --without-recommends -o Dpkg::Options::=--force-confold -o Aptitude::CmdLine::Ignore-Trust-Violations=false -o Aptitude::ProblemResolver::StepScore=100 -o Aptitude::ProblemResolver::SolutionCost="safety, priority, non-default-versions" -o Aptitude::ProblemResolver::Hints::KeepDummy="reject sbuild-build-depends-core-dummy :UNINST" -o Aptitude::ProblemResolver::Keep-All-Level=55000 -o Aptitude::ProblemResolver::Remove-Essential-Level=maximum install vim
  Warning: Invalid locale (please review locale settings, this might lead to problems later):
    locale::facet::_S_create_c_locale name not valid
  The following NEW packages will be installed:
    libgpm2{a} vim vim-common{a} vim-runtime{a} xxd{a} 
  0 packages upgraded, 5 newly installed, 0 to remove and 1 not upgraded.
  Need to get 7225 kB/7260 kB of archives. After unpacking 33.5 MB will be used.
  qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6019d1bf
  qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x601b64ab
  Segmentation fault
  (sid-m68k-sbuild)root@nofan:/#

  The crash does not reproduce on real hardware running Debian unstable.

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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Bug 1815911] Re: aptitude crashes qemu-m68k with handle_cpu_signal received signal outside vCPU context
  2019-02-14 13:53 [Qemu-devel] [Bug 1815911] [NEW] aptitude crashes qemu-m68k with handle_cpu_signal received signal outside vCPU context John Paul Adrian Glaubitz
                   ` (3 preceding siblings ...)
  2020-08-12  6:44 ` John Paul Adrian Glaubitz
@ 2020-08-13 19:13 ` Thomas Huth
  4 siblings, 0 replies; 7+ messages in thread
From: Thomas Huth @ 2020-08-13 19:13 UTC (permalink / raw)
  To: qemu-devel

** Changed in: qemu
       Status: Incomplete => Fix Released

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

Title:
  aptitude crashes qemu-m68k with handle_cpu_signal received signal
  outside vCPU context

Status in QEMU:
  Fix Released

Bug description:
  When building a package with sbuild on Debian, sbuild can use aptitude
  to resolve dependencies.

  Recently, some changes introduced to aptitude or related packages
  cause qemu to crash:

  (sid-m68k-sbuild)root@nofan:/# aptitude -y --without-recommends -o Dpkg::Options::=--force-confold -o Aptitude::CmdLine::Ignore-Trust-Violations=false -o Aptitude::ProblemResolver::StepScore=100 -o Aptitude::ProblemResolver::SolutionCost="safety, priority, non-default-versions" -o Aptitude::ProblemResolver::Hints::KeepDummy="reject sbuild-build-depends-core-dummy :UNINST" -o Aptitude::ProblemResolver::Keep-All-Level=55000 -o Aptitude::ProblemResolver::Remove-Essential-Level=maximum install vim
  Warning: Invalid locale (please review locale settings, this might lead to problems later):
    locale::facet::_S_create_c_locale name not valid
  The following NEW packages will be installed:
    libgpm2{a} vim vim-common{a} vim-runtime{a} xxd{a} 
  0 packages upgraded, 5 newly installed, 0 to remove and 1 not upgraded.
  Need to get 7225 kB/7260 kB of archives. After unpacking 33.5 MB will be used.
  qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6019d1bf
  qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x601b64ab
  Segmentation fault
  (sid-m68k-sbuild)root@nofan:/#

  The crash does not reproduce on real hardware running Debian unstable.

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


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2020-08-13 19:21 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-14 13:53 [Qemu-devel] [Bug 1815911] [NEW] aptitude crashes qemu-m68k with handle_cpu_signal received signal outside vCPU context John Paul Adrian Glaubitz
2019-02-15 12:47 ` [Qemu-devel] [Bug 1815911] " Laurent Vivier
2019-02-16 17:11   ` John Paul Adrian Glaubitz
2020-08-10 15:20 ` Steve Dodd
2020-08-12  6:30 ` Thomas Huth
2020-08-12  6:44 ` John Paul Adrian Glaubitz
2020-08-13 19:13 ` Thomas Huth

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).