Your message dated Mon, 11 Aug 2025 10:45:27 +0300
with message-id <[email protected]>
and subject line Re: Bug#995430: qemu-user-static: creates /core dump
spontaneously upon upgrade, even when not in use?
has caused the Debian Bug report #995430,
regarding qemu-user-static: creates /core dump spontaneously upon upgrade, even
when not in use?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
995430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995430
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-user-static
Version: 1:5.2+dfsg-11
Severity: normal
I noticed a /core file in the root directory, dated around about when
my machine was upgraded to bullseye. I checked another machine, and
it too had the same core file, dated from the upgrade:
24606,4> ls -lA /core
-rw------- 1 root root 11542528 Sep 15 00:41 core
0-0-16:27:43, Fri Oct 01 tconnors@fs:/snapshots/dirac/latest (bash)
24607,5> sudo file core
core: ELF 64-bit LSB core file, x86-64, version 1 (SYSV), SVR4-style, from
'/usr/libexec/qemu-binfmt/s390x-binfmt-P /check /check', real uid: 0, effective
uid: 0, real gid: 0, effective gid: 0, execfn: '/check', platform: 'x86_64'
Working backwards, this was the exact minute this machine was last
rebooted, immediately after being dist-upgraded to bullseye. I
haven't done anything deliberate to fire up qemu from this machine - I
only use it occasionally, and haven't configured it to autostart
anything. Certainly never done anything with S390 on these amd64
boxen.
-- System Information:
Debian Release: 11.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable'), (5, 'testing'), (2, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-8-amd64 (SMP w/24 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
qemu-user-static depends on no packages.
Versions of packages qemu-user-static recommends:
ii binfmt-support 2.2.1-1
Versions of packages qemu-user-static suggests:
ii sudo 1.9.5p2-3
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, 1 May 2022 15:14:57 +0300 Michael Tokarev <[email protected]> wrote:
Control: tag -1 + moreinfo
> core: ELF 64-bit LSB core file, x86-64, version 1 (SYSV), SVR4-style, from
'/usr/libexec/qemu-binfmt/s390x-binfmt-P /check /check', real uid: 0, effective
uid: 0, real gid: 0, effective gid: 0, execfn: '/check', platform: 'x86_64'
Interesting. Do you by a chance also have /check binary?
This is apparently something checking for s390x availability,
so "not in use" is a bit interesting here in this context.
Neither binfmt-support nor systemd does that, and qemu-user-static
does not do this either.
It is interesting twice: the fact someone tried this s390x
abi, and the fact that qemu-s390-static (the binfmt-P is just
a symlink to it) crashed with a core dump. It was run as root
too (well, or else it wouldn't be able to create /core).
It'd be interesting to see the core file and especially the
/check binary.
Did it happen again since that? Can you reinstall qemu-user-static,
or upgrade it again (installing the buster version first) and see
if it triggers the issue again?
This bug report has been in 'moreinfo' state for quite some time,
with no more info available. Nowhere else I see anything like this
happening.
Let's close this bug report now. If you think it is incorrect, feel
free to reopen it and provide some requested information.
Thanks,
/mjt
--- End Message ---
