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

Bug#781715: marked as done (libc-bin: ldconfig crashes with SIGSEGV, with large kernel version value.)



Your message dated Thu, 22 Sep 2022 23:13:51 +0000
with message-id <E1obVOB-00ExA5-4x@fasolo.debian.org>
and subject line Bug#781715: fixed in glibc 2.36-1
has caused the Debian Bug report #781715,
regarding libc-bin: ldconfig crashes with SIGSEGV, with large kernel version value.
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 owner@bugs.debian.org
immediately.)


-- 
781715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781715
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libc-bin
Version: 2.13-38+deb7u8
Severity: important

Hello, whenever ldconfig is run, the following occurs:

# gdb --args ldconfig
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html> This is free software: you are free
to change and redistribute it. There is NO WARRANTY, to the extent
permitted by law.  Type "show copying" and "show warranty" for details.
This GDB was configured as "powerpc-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /sbin/ldconfig...(no debugging symbols
found)...done. (gdb) r
Starting program: /sbin/ldconfig 
Can't read symbols from system-supplied DSO at 0x100000: File truncated
FATAL: cannot determine kernel version

Program received signal SIGSEGV, Segmentation fault.
0x1001a258 in ?? ()
(gdb) bt
#0  0x1001a258 in ?? ()
#1  0x1001a22c in ?? ()
#2  0x1001f6e0 in ?? ()
#3  0x1001f4cc in ?? ()
#4  0x10011aa4 in ?? ()
#5  0x10011c24 in ?? ()
#6  0x10006cb8 in ?? ()
#7  0x10006e40 in ?? ()
#8  0x00000000 in ?? ()
(gdb) info registers
r0             0x100cb8b8	269269176
r1             0xbfffec60	3221220448
r2             0x0	0
r3             0x1000	4096
r4             0x10011aa4	268507812
r5             0x1	1
r6             0xfefefeff	4278124287
r7             0x7f7f7f7f	2139062143
r8             0x80	128
r9             0x100ccc68	269274216
r10            0xffff9028	4294938664
r11            0x100d0000	269287424
r12            0x24004084	603996292
r13            0x100d3fb0	269303728
r14            0x0	0
r15            0x0	0
r16            0x0	0
r17            0x0	0
r18            0x0	0
r19            0x0	0
r20            0x0	0
r21            0x27	39
r22            0x0	0
r23            0x0	0
r24            0x7	7
r25            0xbfffece0	3221220576
r26            0x1	1
r27            0xbfffed24	3221220644
r28            0x100b6458	269182040
r29            0x100d0000	269287424
r30            0x100ccc5c	269274204
r31            0x0	0
pc             0x1001a258	0x1001a258
msr            0xd932	55602
cr             0x24004084	603996292
lr             0x1001a22c	0x1001a22c
ctr            0x1001f6c0	268564160
xer            0x20000000	536870912
orig_r3        0x7	7
trap           0x300	768
(gdb) 

It is possible that it cannot handle my extremely high kernel version
number of 3.14.3720150331. The value 3720150331 exceeds the length of a
signed 32-bit integer. I have never had such a problem before with
lower valued version numbers.

The error appears in a macro called DL_SYSDEP_OSCHECK inside of:
sysdeps/unix/sysv/linux/dl-osinfo.h

''int version = _dl_discover_osversion ();'', which is a signed 32-bit
value.

In sysdeps/unix/sysv/linux/dl-sysdep.c (where _dl_discover_osversion is
defined) that function it operates in an unsigned manner, however it
returns a signed value rather than an unsigned (cast to signed).

-- System Information:
Debian Release: 7.8
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: powerpc (ppc)

Kernel: Linux 3.14.3720150331
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.36-1
Done: Aurelien Jarno <aurel32@debian.org>

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 781715@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno <aurel32@debian.org> (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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 22 Sep 2022 22:23:11 +0200
Source: glibc
Architecture: source
Version: 2.36-1
Distribution: experimental
Urgency: medium
Maintainer: GNU Libc Maintainers <debian-glibc@lists.debian.org>
Changed-By: Aurelien Jarno <aurel32@debian.org>
Closes: 781715 996598 1004577
Changes:
 glibc (2.36-1) experimental; urgency=medium
 .
   [ Aurelien Jarno ]
   * New upstream release:
     - Support for DT_RELR relative relocation format has been added.  Closes:
       #996598.
     - The Linux kernel version check has been removed.  Closes: #781715, #1004577.
     - debian/symbols.wildcard: add 2.36 and GLIBC_ABI_DT_RELR.
     - debian/patches/localedata/sort-UTF8-first.diff: rebased.
     - debian/patches/localedata/supported.diff: rebased.
     - debian/patches/arm/unsubmitted-ldso-multilib.diff: rebased.
     - debian/patches/hurd-i386/git-spawni-reauth.diff: upstreamed.
     - debian/patches/hurd-i386/pthread_key.diff: upstreamed.
     - debian/patches/kfreebsd/submitted-waitid.diff: dropped. kfreebsd
       specific changes moved to debian/patches/kfreebsd/local-sysdeps.diff.
     - debian/patches/kfreebsd/local-config_h_in.patch: rebased.
     - debian/patches/kfreebsd/local-getaddrinfo-freebsd-kernel.diff: rebased.
     - debian/patches/all/local-remove-manual.diff: rebased.
     - debian/patches/any/local-ldso-disable-hwcap.diff: rebased.
     - debian/patches/any/unsubmitted-ldso-machine-mismatch.diff: rebased.
     - debian/patches/any/submitted-resolv-unaligned.diff: upstreamed.
     - debian/patches/hurd-i386/local-fix-nss.diff: rebased.
     - debian/patches/hurd-i386/local-no-bootstrap-fs-access.2.diff: rebased.
 .
   [ Samuel Thibault ]
   * debian/testsuite-xfail-debian.mk: Update tests results for hurd-i386.
Checksums-Sha1:
 42153796cedd3511957ea5621a9ab89fd5301b4d 9679 glibc_2.36-1.dsc
 d034128a6116dcf9e76c92f898ec63f4f4e65786 19363988 glibc_2.36.orig.tar.xz
 27a822a7c20d1e9c534ef43f259dbd50c9192348 807616 glibc_2.36-1.debian.tar.xz
 8331b65015d31d73d7a7ad102e1f7667dc43662a 9567 glibc_2.36-1_source.buildinfo
Checksums-Sha256:
 a3ef663a56bdf3fa3a0c07ce665edd650e4c7d5897e201eba775ceeffa93fab1 9679 glibc_2.36-1.dsc
 a543c02070d46ccaf866957efd13f10c924daa74c86a90a0254db09a92a708ee 19363988 glibc_2.36.orig.tar.xz
 b19408b4f8780ee9c40e1ba6ba17e0b6bfc1007fb4a668784dce77d6bc87f516 807616 glibc_2.36-1.debian.tar.xz
 bd1df4ee606e46ba5b67230eced1a93bec5ca278a558c77f162a9edde44aceee 9567 glibc_2.36-1_source.buildinfo
Files:
 dbf98687737cd10090ab5d3567bc1733 9679 libs required glibc_2.36-1.dsc
 b2b0246bc50781a2243f8141feeb1bf4 19363988 libs required glibc_2.36.orig.tar.xz
 5935c135f2ac1afe0bbec46a3c758acf 807616 libs required glibc_2.36-1.debian.tar.xz
 74d6e6af9a8c71bc4df15256cba215c9 9567 libs required glibc_2.36-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmMsx7kACgkQE4jA+Jno
M2szmQ/9GKpKoy+w73uz7jJl9gxxtKjFZo1q103jjRXMviFgX3KbbmWZl2wNOM5N
gPflh/5gLS6cBmEJhRoOXR42uldBiNkLigYGdfDul9+lX0PckcoIYC0pE/a+5/dC
+iCTus22eLq412vWvKipxwXaisSnt1RNg7UwtLosnlDJehvQFGC3SzANMw8RgQPr
GpUQaSYHJJnx0bx9gZUgcNJzMNUzFVaealQID18I0vWqS3Ui1szTva/esLL6iFN0
yMuYTYdYTjhkul6X8Wz00OaWLwkPrS3H2A7Wywm1myNih+e6PRILkMrgFvMzpPaK
OJhjhh4cAO2+v3lDKGWPugsUGPGPzd2OixHU9Lb6vwO/GAHx9Gw0b5+cik7tYkHF
wmZSHudqntfF8kuJQ0P2jkeH8J0yKX+tTg+jhaR0tYZNvcxnZla0IZhygXZUVQWj
LKb4yW/8BpeVQlvvD+M6GeMvRal9iX1Ci0afFb/TBNeCgg3um9UiCYzaaLWGoEkO
e1x1bgQY7thxmAoQec5DCDKo1tYIMZeU4cvc6ojfbEdGejPDVlMSDu1A4BbMLsdQ
z9n6nH6OVy0SNikZUhdTzI5JwqwItpd4GdCX8XKZj5GKdhKLnGcGgPfjojDgwYg3
hgS6D8/nUeJ1ElW2waQRt2FFlvkUCBjYZn1n4+CRGX+4/AeHy1s=
=jG2P
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: