[Git][glibc-team/glibc][sid] hurd: fix default character for termio cc[VSTATE]
Samuel Thibault pushed to branch sid at GNU Libc Maintainers / glibc Commits: 9bb7cc7e by Samuel Thibault at 2022-01-07T00:25:56+01:00 hurd: fix default character for termio cc[VSTATE] * debian/patches/hurd-i386/git-ttydefaults.diff - - - - - 3 changed files: - debian/changelog - + debian/patches/hurd-i386/git-ttydefaults.diff - debian/patches/series View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/9bb7cc7e59f3d86c515a664a9a25911e4466eb86 -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/9bb7cc7e59f3d86c515a664a9a25911e4466eb86 You're receiving this email because of your account on salsa.debian.org.
glibc_2.33-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 06 Jan 2022 22:32:53 +0100 Source: glibc Architecture: source Version: 2.33-2 Distribution: unstable Urgency: medium Maintainer: GNU Libc Maintainers Changed-By: Aurelien Jarno Closes: 1003201 Changes: glibc (2.33-2) unstable; urgency=medium . [ Samuel Thibault ] * debian/patches/hurd-i386/unsubmitted-getaux_at_secure.diff: Fix according to new __getauxval2 function. * debian/libc0.3.symbols.hurd-i386: Add vm_region_create_proxy. * debian/patches/hurd-i386/git-lib-map.diff: Unlock libraries load addresses. * debian/patches/hurd-i386/git-large-text.diff: Fix clang startup. * debian/patches/hurd-i386/git-get_dtable.diff: Implement msg_get_dtable. * debian/patches/hurd-i386/git-auth-leak.diff: Fix auth port leaks. * debian/patches/hurd-i386/git-nuke_ports_on_exec.diff: Fix ports leaks. * debian/testsuite-xfail-debian.mk: Update hurd tests. . [ Aurelien Jarno ] * debian/patches/git-updates.diff: update from upstream stable branch: - Fix syscall() on ppc64 with POWER9 CPUs. Closes: #1003201. Checksums-Sha1: 3ea45e4dbbdce3af7a27f0c31b3fea31e6e3017b 9618 glibc_2.33-2.dsc a483da05e911e2fc952d77dc75cf00643b76cc21 811704 glibc_2.33-2.debian.tar.xz dd44fb4d94a81c5a7c73558907c92648b25d61b4 8829 glibc_2.33-2_source.buildinfo Checksums-Sha256: ea635876d001360999c88093af939ab09ba3667854eaeca3d249bc9dacfb311c 9618 glibc_2.33-2.dsc 7a4f5334dd48bdf977b012f68e243d25752a8bf0aae7995d8d461ff8fff3f97a 811704 glibc_2.33-2.debian.tar.xz 26862df06c18c38f3ea13c3c9a6a67310c515fd6e71f9a3a732204005617edcb 8829 glibc_2.33-2_source.buildinfo Files: 07636be19dea8f0d70efcffc44494af4 9618 libs required glibc_2.33-2.dsc a2ce0eaff86a0924c0d090736adfa1af 811704 libs required glibc_2.33-2.debian.tar.xz 3780fcae85376ce5943e384d456cd201 8829 libs required glibc_2.33-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmHXZN0ACgkQE4jA+Jno M2sXDA//YwKmoyN3zmAy42nZ8GmlIuOC3kKEqGY4J5n9yWBCokXnBQn8B8zIwzvy I6WFu6wpwN5zhNhcR7Wc2TwPDzckai0zjTZMehOIvjCBSaaKluSqtyAn7FfaypJf jo2PPfYKZ/XiRzvC4vRylcumxt/aIU10ZUG+AzVp4OFiJq/yjOSd9qP86zyatqbQ XyTG/bW7wjxXFcMV2/7ObcPvfA6RlFjypKrFylalVArPHbbQcaSJ5CiYaVtrDGzH txnYMNB/UgfgiFPY0cQzIk1ky+F1xw/tQKJRO2fiRRpT/x1q1vRfE/+6rufBBG6z sxLib/zNAvbSTb9HzSXaO+SMCusRq4cCJYcIrkEvkPoIY55z/rRMM7luXKMc3+Bc w2oQVbr8S2WwfIDPpvpKed6FFq+qnfZmbPN2M+/22LcJe7ukabsDEPoGKuIClGfT O+LFnU5DSsfz29k6U/LHr+jCo0Vxe1vhXznPFvyt1S9VGKMotTWWNIMGS5Ea2XoW vx4KkAiLpG/c6N0IJ/k9O03rQXD125QvRZQxiz7CeA9iSkM3ChJ0ysoMhiefmU/p ELrTW7IHu1v8VprklvoycnkiS0NS66zNvZBQrpR59wfQQl7nFWMqHNlSLeJOScKA vRHgQuZ5mAVNHnU9ki51Lj00oe6qXaZc7k1keHOtTgOF0QJJz94= =lD2b -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of glibc_2.33-2_source.changes
glibc_2.33-2_source.changes uploaded successfully to localhost along with the files: glibc_2.33-2.dsc glibc_2.33-2.debian.tar.xz glibc_2.33-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#1003201: marked as done (libc6: Upgrading to libc 2.33-1 causes lots of strange crashes)
Your message dated Thu, 06 Jan 2022 22:03:45 + with message-id and subject line Bug#1003201: fixed in glibc 2.33-2 has caused the Debian Bug report #1003201, regarding libc6: Upgrading to libc 2.33-1 causes lots of strange crashes 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 ow...@bugs.debian.org immediately.) -- 1003201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libc6 Version: 2.33-1 Severity: important X-Debbugs-Cc: rincebr...@gmail.com Dear Maintainer, (I marked this as serious because it's "just" ppc64, but the system is permaneantly unusable if this upgrade is installed.) I booted my ppc64 VM in qemu 6.1, apt update, apt upgrade, and 20-30 packages in, it died horribly with Python3 packages erroring out with "Cannot get content of [whatever package]". Trying to log into a shell over ssh or at a tty after this happens dies with an error that flashes fast, but but seems to be "free(): invalid pointer" Random applications will now just crash out, in addition to the obvious. (I'm writing this from a session spawned before the upgrade, which can still spawn children successfully until I log out.) If I reboot after upgrading, all services fail to start on boot, and it never spawns a login prompt or rescue prompt, it just sits forever on a list of failed service starts. Anything that would be helpful to debug this? I have a snapshot of the VM before this began, so I can just roll it back and repeat the exercise. - Rich -- System Information: Debian Release: bookworm/sid Architecture: powerpc64 (ppc64) Kernel: Linux 5.15.0-2-powerpc64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: glibc Source-Version: 2.33-2 Done: Aurelien Jarno We believe that the bug you reported is fixed in the latest version of glibc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1003...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurelien Jarno (supplier of updated glibc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 06 Jan 2022 22:32:53 +0100 Source: glibc Architecture: source Version: 2.33-2 Distribution: unstable Urgency: medium Maintainer: GNU Libc Maintainers Changed-By: Aurelien Jarno Closes: 1003201 Changes: glibc (2.33-2) unstable; urgency=medium . [ Samuel Thibault ] * debian/patches/hurd-i386/unsubmitted-getaux_at_secure.diff: Fix according to new __getauxval2 function. * debian/libc0.3.symbols.hurd-i386: Add vm_region_create_proxy. * debian/patches/hurd-i386/git-lib-map.diff: Unlock libraries load addresses. * debian/patches/hurd-i386/git-large-text.diff: Fix clang startup. * debian/patches/hurd-i386/git-get_dtable.diff: Implement msg_get_dtable. * debian/patches/hurd-i386/git-auth-leak.diff: Fix auth port leaks. * debian/patches/hurd-i386/git-nuke_ports_on_exec.diff: Fix ports leaks. * debian/testsuite-xfail-debian.mk: Update hurd tests. . [ Aurelien Jarno ] * debian/patches/git-updates.diff: update from upstream stable branch: - Fix syscall() on ppc64 with POWER9 CPUs. Closes: #1003201. Checksums-Sha1: 3ea45e4dbbdce3af7a27f0c31b3fea31e6e3017b 9618 glibc_2.33-2.dsc a483da05e911e2fc952d77dc75cf00643b76cc21 811704 glibc_2.33-2.debian.tar.xz dd44fb4d94a81c5a7c73558907c92648b25d61b4 8829 glibc_2.33-2_source.buildinfo Checksums-Sha256: ea635876d001360999c88093af939ab09ba3667854eaeca3d249bc9dacfb311c 9618 glibc_2.33-2.dsc 7a4f5334dd48bdf977b012f68e243d25752a8bf0aae7995d8d461ff8fff3f97a 811704 glibc_2.33-2.debian.tar.xz 26862df06c18c38f3ea13c3c9a6a67310c515fd6e71f9a3a732204005617edcb 8829 glibc_2.33-2_source.buildinfo Files: 07636be19dea8f0d70efcffc44494af4 9618 libs required glibc_2.33-2.dsc a2ce0eaff86a0924c0d090736adfa1af 811704 libs required glibc_2.33-2.debian.tar.xz 3780fcae85376ce5943e384d456cd201 8829 libs required glibc_2.33-2_source.buildinfo -B
Processed: Bug#1003201 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1003201 [libc6] libc6: Upgrading to libc 2.33-1 causes lots of strange crashes Ignoring request to alter tags of bug #1003201 to the same tags previously set -- 1003201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
[Git][glibc-team/glibc][glibc-2.34] 4 commits: Note upstream commit ids
Aurelien Jarno pushed to branch glibc-2.34 at GNU Libc Maintainers / glibc Commits: 6c5717f3 by Samuel Thibault at 2022-01-06T15:53:33+01:00 Note upstream commit ids - - - - - 8de2e937 by Aurelien Jarno at 2022-01-06T22:30:11+01:00 debian/patches/git-updates.diff: update from upstream stable branch: * debian/patches/git-updates.diff: update from upstream stable branch: - Fix syscall() on ppc64 with POWER9 CPUs. Closes: #1003201. - - - - - 9e66c645 by Aurelien Jarno at 2022-01-06T22:32:59+01:00 releasing package glibc version 2.33-2 - - - - - 2851bb4b by Aurelien Jarno at 2022-01-06T22:54:24+01:00 Merge branch 'sid' into glibc-2.34 - - - - - 7 changed files: - debian/changelog - debian/patches/hurd-i386/git-auth-leak.diff - debian/patches/hurd-i386/git-get_dtable.diff - debian/patches/hurd-i386/git-large-text.diff - debian/patches/hurd-i386/git-lib-map.diff - debian/patches/hurd-i386/git-msync.diff - debian/patches/hurd-i386/git-nuke_ports_on_exec.diff View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/compare/c438452ee192f6dc61b3addcae6c80c3055ab2b7...2851bb4b155ec64f930874f969093436c03b8ce4 -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/compare/c438452ee192f6dc61b3addcae6c80c3055ab2b7...2851bb4b155ec64f930874f969093436c03b8ce4 You're receiving this email because of your account on salsa.debian.org.
[Git][glibc-team/glibc] Pushed new tag debian/2.33-2
Aurelien Jarno pushed new tag debian/2.33-2 at GNU Libc Maintainers / glibc -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/tree/debian/2.33-2 You're receiving this email because of your account on salsa.debian.org.
[Git][glibc-team/glibc][sid] releasing package glibc version 2.33-2
Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc Commits: 9e66c645 by Aurelien Jarno at 2022-01-06T22:32:59+01:00 releasing package glibc version 2.33-2 - - - - - 1 changed file: - debian/changelog View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/9e66c645b1e623b85e4bbb74d3dfa1e36d7427cb -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/9e66c645b1e623b85e4bbb74d3dfa1e36d7427cb You're receiving this email because of your account on salsa.debian.org.
Processed: Bug#1003201 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #1003201 [libc6] libc6: Upgrading to libc 2.33-1 causes lots of strange crashes Added tag(s) pending. -- 1003201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003201: libc6: Upgrading to libc 2.33-1 causes lots of strange crashes
On 2022-01-06 05:36, Rich wrote: > On Thu, Jan 6, 2022 at 5:22 AM Aurelien Jarno wrote: > > > On 2022-01-06 03:36, Rich wrote: > > > Hi Aurelien, > > > It's a VM running in qemu on an amd64 Debian bullseye system, no KVM > > > acceleration to be found here. > > > > Ok, that might be a QEMU issue then. Which CPU do you emulate with QEMU? > > > > I don't explicitly specify a -M or -cpu, so whatever it defaults to, which > according to -M help seems to be "pseries" mapping to pseries-6.1 here. Thanks. That allowed me to reproduce the issue locally. I tracked down it was due to the emulation of a POWER9 CPU, things work fine with a POWER8 CPU. I found that it has been fixed recently in the upstream 2.33 branch: https://sourceware.org/git/?p=glibc.git;a=commit;h=c493f6a0e4dcd6fff22da0df9fb2e52ecf41 -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
[Git][glibc-team/glibc][sid] debian/patches/git-updates.diff: update from upstream stable branch:
Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc Commits: 8de2e937 by Aurelien Jarno at 2022-01-06T22:30:11+01:00 debian/patches/git-updates.diff: update from upstream stable branch: * debian/patches/git-updates.diff: update from upstream stable branch: - Fix syscall() on ppc64 with POWER9 CPUs. Closes: #1003201. - - - - - 2 changed files: - debian/changelog - debian/patches/git-updates.diff View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/8de2e93716988a311fb0075493feb386cf6adf93 -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/8de2e93716988a311fb0075493feb386cf6adf93 You're receiving this email because of your account on salsa.debian.org.
[Git][glibc-team/glibc][sid] Note upstream commit ids
Samuel Thibault pushed to branch sid at GNU Libc Maintainers / glibc Commits: 6c5717f3 by Samuel Thibault at 2022-01-06T15:53:33+01:00 Note upstream commit ids - - - - - 6 changed files: - debian/patches/hurd-i386/git-auth-leak.diff - debian/patches/hurd-i386/git-get_dtable.diff - debian/patches/hurd-i386/git-large-text.diff - debian/patches/hurd-i386/git-lib-map.diff - debian/patches/hurd-i386/git-msync.diff - debian/patches/hurd-i386/git-nuke_ports_on_exec.diff View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/6c5717f3ac95238f7f84af0204fe820b9ea3baa9 -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/6c5717f3ac95238f7f84af0204fe820b9ea3baa9 You're receiving this email because of your account on salsa.debian.org.
Bug#1003213: locales-all: introduce locales-utf8 package?
Package: locales-all Version: 2.33-1 Severity: wishlist As discussed recently on -devel and previously in #701585, at the moment Debian users have a choice between two non-ideal locale setups: * install locales and generate a subset of locale files with locale-gen (this is optimal for small systems, but it's difficult for high-level UIs like GNOME Settings to present this to users, particularly in a non-distro-specific way) * install locales-all (this costs > 200M but ensures that all locales are available) For "reasonably large" desktop and server systems, I wonder whether it might be better to generate a subset of locales-all with just the UTF-8 locales that we recommend for general use, and install that by default? If I'm counting correctly, that would be about 100M, which is perhaps an acceptable price to pay for language settings being straightforward - a reasonably complete set of Noto fonts (without CJK) is already more than half of that. locales-all could have a Depends on locales-utf8 and contain the remaining (legacy national character set) locales, if anyone still needs that. locales-utf8 would probably also be enough for many locale-sensitive packages' test suites. smcv
Bug#1003201: libc6: Upgrading to libc 2.33-1 causes lots of strange crashes
On Thu, Jan 6, 2022 at 5:22 AM Aurelien Jarno wrote: > On 2022-01-06 03:36, Rich wrote: > > Hi Aurelien, > > It's a VM running in qemu on an amd64 Debian bullseye system, no KVM > > acceleration to be found here. > > Ok, that might be a QEMU issue then. Which CPU do you emulate with QEMU? > I don't explicitly specify a -M or -cpu, so whatever it defaults to, which according to -M help seems to be "pseries" mapping to pseries-6.1 here. - Rich - Rich > > Regards, > Aurelien > > -- > Aurelien Jarno GPG: 4096R/1DDD8C9B > aurel...@aurel32.net http://www.aurel32.net >
Bug#1003201: libc6: Upgrading to libc 2.33-1 causes lots of strange crashes
On 2022-01-06 03:36, Rich wrote: > Hi Aurelien, > It's a VM running in qemu on an amd64 Debian bullseye system, no KVM > acceleration to be found here. Ok, that might be a QEMU issue then. Which CPU do you emulate with QEMU? Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#1003201: libc6: Upgrading to libc 2.33-1 causes lots of strange crashes
https://www.dropbox.com/s/k117zefr83k6b11/ppc64%20bt.png?dl=0 is the backtrace gdb reports from that core, helpful as it is. I actually originally had this happen on qemu 5.2, then I upgraded to 6.1 to see if it went away (it does not, and it happily reproduces on fresh upgrade each time). - Rich On Thu, Jan 6, 2022 at 3:36 AM Rich wrote: > Hi Aurelien, > It's a VM running in qemu on an amd64 Debian bullseye system, no KVM > acceleration to be found here. > > dmesg doesn't have any backtraces - the two messages that show up are > py3compile segfaulting with all the addresses printed as instead, > and a couple of programs (like mandb) reporting getting a pointer of > 0xfff1 or similar and dying in a fire. > > The first ones after the upgrade: > Jan 6 01:30:39 encrepro kernel: [ 6715.078626] mandb[1903]: User access > of kernel address (8408) - exploit attempt? (uid: 6) > Jan 6 01:30:39 encrepro kernel: [ 6715.093977] mandb[1903]: segfault (11) > at 8408 nip 7fffb37f5f28 lr 7fffb37f5f08 code 1 in > libseccomp.so.2.5.3[7fffb37f+3] > Jan 6 01:30:39 encrepro kernel: [ 6715.100149] mandb[1903]: code: > fbe10078 3880 7c7f1b78 4bffddfd e8410028 2c03 41800030 ebe10078 > Jan 6 01:30:39 encrepro kernel: [ 6715.100308] mandb[1903]: code: > 3860 38210080 6000 e8010010 <906283f8> 7c6307b4 7c0803a6 4e800020 > Jan 6 01:31:31 encrepro kernel: [ 6767.287646] reportbug[1982]: segfault > (11) at 34c8 nip 34c8 lr 34c8 code 1 in python3.9[1000+5d] > Jan 6 01:31:31 encrepro kernel: [ 6767.293334] reportbug[1982]: code: > > Jan 6 01:31:31 encrepro kernel: [ 6767.293545] reportbug[1982]: code: > > > And later: > > Jan 6 01:35:30 encrepro systemd[2290]: free(): invalid pointer > > and > > Jan 6 01:42:53 encrepro systemd[1]: Created slice User Slice of UID 1000. > Jan 6 01:42:53 encrepro systemd[1]: Starting User Runtime Directory > /run/user/1000... > Jan 6 01:42:53 encrepro systemd[1]: Finished User Runtime Directory > /run/user/1000. > Jan 6 01:42:53 encrepro systemd[1]: Starting User Manager for UID 1000... > Jan 6 01:42:53 encrepro systemd[2370]: free(): invalid pointer > Jan 6 01:42:54 encrepro systemd[1]: user@1000.service: Main process > exited, code=killed, status=6/ABRT > Jan 6 01:42:54 encrepro systemd[1]: user@1000.service: Failed with > result 'signal'. > Jan 6 01:42:54 encrepro systemd[1]: Failed to start User Manager for UID > 1000. > > I've got a core dump from mandb: > https://www.dropbox.com/s/4z6bfbuluwub29r/ppc64_libc?dl=0 > > I don't have a stacktrace from it, though, since I didn't already have gdb > on the VM, and it wants to upgrade libc to install. (I know I could go find > an appropriately old section of snapshots.debian.org, but haven't done > that yet...) > > - Rich > > On Thu, Jan 6, 2022 at 3:13 AM Aurelien Jarno > wrote: > >> control: tag -1 + help >> control: user debian-powe...@lists.debian.org >> control: usertag -1 ppc64 >> >> On 2022-01-06 01:45, Rich Ercolani wrote: >> > Package: libc6 >> > Version: 2.33-1 >> > Severity: important >> > X-Debbugs-Cc: rincebr...@gmail.com >> > >> > Dear Maintainer, >> > >> > (I marked this as serious because it's "just" ppc64, but the system is >> permaneantly unusable if this upgrade is installed.) >> >> I have added the powerpc list in Cc: as the ppc64 porters are the people >> who can help you there. >> >> > I booted my ppc64 VM in qemu 6.1, apt update, apt upgrade, and 20-30 >> packages in, it died horribly >> > with Python3 packages erroring out with "Cannot get content of >> [whatever package]". >> >> Is it a VM running with KVM or is it using QEMU emulation? >> >> > Trying to log into a shell over ssh or at a tty after this happens dies >> with an error that flashes fast, but >> > but seems to be "free(): invalid pointer" >> > >> > Random applications will now just crash out, in addition to the >> obvious. (I'm writing this from a session >> > spawned before the upgrade, which can still spawn children successfully >> until I log out.) >> > >> > If I reboot after upgrading, all services fail to start on boot, and it >> never spawns a login prompt or rescue >> > prompt, it just sits forever on a list of failed service starts. >> > >> > Anything that would be helpful to debug this? I have a snapshot of the >> VM before this began, so I can >> > just roll it back and repeat the exercise. >> >> Ideally a backtrace would help, dmesg outputs can also be useful, >> however given the state of you system, they might be difficult to get. >> >> Regards, >> Aurelien >> >> -- >> Aurelien Jarno GPG: 4096R/1DDD8C9B >> aurel...@aurel32.net http://www.aurel32.net >> >
Bug#1003201: libc6: Upgrading to libc 2.33-1 causes lots of strange crashes
Hello! On 1/6/22 09:13, Aurelien Jarno wrote: >> (I marked this as serious because it's "just" ppc64, but the system is >> permaneantly unusable if this upgrade is installed.) > > I have added the powerpc list in Cc: as the ppc64 porters are the people > who can help you there. > >> I booted my ppc64 VM in qemu 6.1, apt update, apt upgrade, and 20-30 >> packages in, it died horribly >> with Python3 packages erroring out with "Cannot get content of [whatever >> package]". > > Is it a VM running with KVM or is it using QEMU emulation? I haven't seen any such issues on the powerpc/ppc64 buildds, but I will check whether I can reproduce this problem on my iBook G4 which has an older processor in case this is a regression that affects older machines only. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1003201: libc6: Upgrading to libc 2.33-1 causes lots of strange crashes
Hi Aurelien,
It's a VM running in qemu on an amd64 Debian bullseye system, no KVM
acceleration to be found here.
dmesg doesn't have any backtraces - the two messages that show up are
py3compile segfaulting with all the addresses printed as instead,
and a couple of programs (like mandb) reporting getting a pointer of
0xfff1 or similar and dying in a fire.
The first ones after the upgrade:
Jan 6 01:30:39 encrepro kernel: [ 6715.078626] mandb[1903]: User access of
kernel address (8408) - exploit attempt? (uid: 6)
Jan 6 01:30:39 encrepro kernel: [ 6715.093977] mandb[1903]: segfault (11)
at 8408 nip 7fffb37f5f28 lr 7fffb37f5f08 code 1 in
libseccomp.so.2.5.3[7fffb37f+3]
Jan 6 01:30:39 encrepro kernel: [ 6715.100149] mandb[1903]: code: fbe10078
3880 7c7f1b78 4bffddfd e8410028 2c03 41800030 ebe10078
Jan 6 01:30:39 encrepro kernel: [ 6715.100308] mandb[1903]: code: 3860
38210080 6000 e8010010 <906283f8> 7c6307b4 7c0803a6 4e800020
Jan 6 01:31:31 encrepro kernel: [ 6767.287646] reportbug[1982]: segfault
(11) at 34c8 nip 34c8 lr 34c8 code 1 in python3.9[1000+5d]
Jan 6 01:31:31 encrepro kernel: [ 6767.293334] reportbug[1982]: code:
Jan 6 01:31:31 encrepro kernel: [ 6767.293545] reportbug[1982]: code:
And later:
Jan 6 01:35:30 encrepro systemd[2290]: free(): invalid pointer
and
Jan 6 01:42:53 encrepro systemd[1]: Created slice User Slice of UID 1000.
Jan 6 01:42:53 encrepro systemd[1]: Starting User Runtime Directory
/run/user/1000...
Jan 6 01:42:53 encrepro systemd[1]: Finished User Runtime Directory
/run/user/1000.
Jan 6 01:42:53 encrepro systemd[1]: Starting User Manager for UID 1000...
Jan 6 01:42:53 encrepro systemd[2370]: free(): invalid pointer
Jan 6 01:42:54 encrepro systemd[1]: user@1000.service: Main process
exited, code=killed, status=6/ABRT
Jan 6 01:42:54 encrepro systemd[1]: user@1000.service: Failed with result
'signal'.
Jan 6 01:42:54 encrepro systemd[1]: Failed to start User Manager for UID
1000.
I've got a core dump from mandb:
https://www.dropbox.com/s/4z6bfbuluwub29r/ppc64_libc?dl=0
I don't have a stacktrace from it, though, since I didn't already have gdb
on the VM, and it wants to upgrade libc to install. (I know I could go find
an appropriately old section of snapshots.debian.org, but haven't done that
yet...)
- Rich
On Thu, Jan 6, 2022 at 3:13 AM Aurelien Jarno wrote:
> control: tag -1 + help
> control: user debian-powe...@lists.debian.org
> control: usertag -1 ppc64
>
> On 2022-01-06 01:45, Rich Ercolani wrote:
> > Package: libc6
> > Version: 2.33-1
> > Severity: important
> > X-Debbugs-Cc: rincebr...@gmail.com
> >
> > Dear Maintainer,
> >
> > (I marked this as serious because it's "just" ppc64, but the system is
> permaneantly unusable if this upgrade is installed.)
>
> I have added the powerpc list in Cc: as the ppc64 porters are the people
> who can help you there.
>
> > I booted my ppc64 VM in qemu 6.1, apt update, apt upgrade, and 20-30
> packages in, it died horribly
> > with Python3 packages erroring out with "Cannot get content of [whatever
> package]".
>
> Is it a VM running with KVM or is it using QEMU emulation?
>
> > Trying to log into a shell over ssh or at a tty after this happens dies
> with an error that flashes fast, but
> > but seems to be "free(): invalid pointer"
> >
> > Random applications will now just crash out, in addition to the obvious.
> (I'm writing this from a session
> > spawned before the upgrade, which can still spawn children successfully
> until I log out.)
> >
> > If I reboot after upgrading, all services fail to start on boot, and it
> never spawns a login prompt or rescue
> > prompt, it just sits forever on a list of failed service starts.
> >
> > Anything that would be helpful to debug this? I have a snapshot of the
> VM before this began, so I can
> > just roll it back and repeat the exercise.
>
> Ideally a backtrace would help, dmesg outputs can also be useful,
> however given the state of you system, they might be difficult to get.
>
> Regards,
> Aurelien
>
> --
> Aurelien Jarno GPG: 4096R/1DDD8C9B
> aurel...@aurel32.net http://www.aurel32.net
>
Processed (with 2 errors): Re: Bug#1003201: libc6: Upgrading to libc 2.33-1 causes lots of strange crashes
Processing control commands: > tag -1 + help Bug #1003201 [libc6] libc6: Upgrading to libc 2.33-1 causes lots of strange crashes Added tag(s) help. > user debian-powe...@lists.debian.org Unknown command or malformed arguments to command. > usertag -1 ppc64 Unknown command or malformed arguments to command. -- 1003201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003201: libc6: Upgrading to libc 2.33-1 causes lots of strange crashes
control: tag -1 + help control: user debian-powe...@lists.debian.org control: usertag -1 ppc64 On 2022-01-06 01:45, Rich Ercolani wrote: > Package: libc6 > Version: 2.33-1 > Severity: important > X-Debbugs-Cc: rincebr...@gmail.com > > Dear Maintainer, > > (I marked this as serious because it's "just" ppc64, but the system is > permaneantly unusable if this upgrade is installed.) I have added the powerpc list in Cc: as the ppc64 porters are the people who can help you there. > I booted my ppc64 VM in qemu 6.1, apt update, apt upgrade, and 20-30 packages > in, it died horribly > with Python3 packages erroring out with "Cannot get content of [whatever > package]". Is it a VM running with KVM or is it using QEMU emulation? > Trying to log into a shell over ssh or at a tty after this happens dies with > an error that flashes fast, but > but seems to be "free(): invalid pointer" > > Random applications will now just crash out, in addition to the obvious. (I'm > writing this from a session > spawned before the upgrade, which can still spawn children successfully until > I log out.) > > If I reboot after upgrading, all services fail to start on boot, and it never > spawns a login prompt or rescue > prompt, it just sits forever on a list of failed service starts. > > Anything that would be helpful to debug this? I have a snapshot of the VM > before this began, so I can > just roll it back and repeat the exercise. Ideally a backtrace would help, dmesg outputs can also be useful, however given the state of you system, they might be difficult to get. Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
