Your message dated Fri, 03 May 2024 20:49:31 +0000
with message-id <e1s2zqv-008ttu...@fasolo.debian.org>
and subject line Bug#1042562: fixed in glibc 2.38-7
has caused the Debian Bug report #1042562,
regarding libc6: broken utmp handling in 32-bit programs with 64-bit time_t
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.)


-- 
1042562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.37-6
Tags: upstream

The utmp(5) interface has broken its compatibility in 32-bit programs
built with -D_TIME_BITS=64.  In bits/utmpx.h we see this:

,----
| /* The fields ut_session and ut_tv must be the same size when compiled
|    32- and 64-bit.  This allows files and shared memory to be shared
|    between 32- and 64-bit applications.  */
| #if __WORDSIZE_TIME64_COMPAT32
|   __int32_t ut_session;               /* Session ID, used for windowing.  */
|   struct
|   {
|     __int32_t tv_sec;         /* Seconds.  */
|     __int32_t tv_usec;                /* Microseconds.  */
|   } ut_tv;                    /* Time entry was made.  */
| #else
|   long int ut_session;                /* Session ID, used for windowing.  */
|   struct timeval ut_tv;               /* Time entry was made.  */
| #endif
`----

The definition of __WORDSIZE_TIME64_COMPAT32 can be found in bits/wordsize.h:

,----
| #ifdef __x86_64__
| # define __WORDSIZE_TIME64_COMPAT32   1
| /* Both x86-64 and x32 use the 64-bit system call interface.  */
| # define __SYSCALL_WORDSIZE           64
| #else
| # define __WORDSIZE_TIME64_COMPAT32   0
| #endif
`----

So on i386 (and I suppose on other 32-bit architectures except x32)
ut_tv is of struct timeval, and ut_tv.tv_sec is of time_t, which is
actually a 64-bit integer in programs built with -D_TIME_BITS=64.

One example where this already has caused problems is the who(1) program
which has opted in for -D_TIME_BITS=64, see #1027135.  Once programs
start to _write_ utmp entries with a 64-bit ut_tv.tv_sec rather than
merely reading them, things could become more interesting. :-(


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.38-7
Done: Aurelien Jarno <aure...@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 1042...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

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


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

Format: 1.8
Date: Fri, 03 May 2024 21:55:28 +0200
Source: glibc
Architecture: source
Version: 2.38-7
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers <debian-glibc@lists.debian.org>
Changed-By: Aurelien Jarno <aure...@debian.org>
Closes: 1042562
Changes:
 glibc (2.38-7) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * debian/patches/hurd-i386/git-context.diff: Add hurd-amd64 version of
     *context.
   * debian/testsuite-xfail-debian.mk: Update hurd-amd64-specific xfails
     accordingly.
   * debian/patches/hurd-i386/local-no-bootstrap-fs-access.2.diff: Also update
     localplt.data on hurd-amd64.
   * debian/patches/hurd-i386/local-stack_chk_guard.diff: Also update
     ld.abilist on hurd-amd64.
   * debian/patches/hurd-i386/local-exec_filename.diff: Also update
     libc.abilist on hurd-amd64.
   * debian/patches/hurd-i386/local-usr.diff: Also update libc.abilist on
     hurd-amd64.
 .
   [ Aurelien Jarno ]
   * debian/patches/any/git-test-epoll.diff: improve test-epoll robustness
     improvements from upstream, useful when running the testsuite on
     overloaded hosts.
   * debian/patches/git-updates.diff: update from upstream stable branch:
     - Fix utmp handling in 32-bit programs when using -D_TIME_BITS=64.
       Closes: #1042562.
Checksums-Sha1:
 2cc660b009ea9028c240a88064b05740237ff860 9079 glibc_2.38-7.dsc
 32442f4ebdcf7cabbd9fab979c7db6b47fa4f6ae 426224 glibc_2.38-7.debian.tar.xz
 560e43e1a854511e54ea90052979ecae44a90189 10084 glibc_2.38-7_source.buildinfo
Checksums-Sha256:
 1ccf3bd21cec30151ce8a69c0fbcce9cbdeca85f979aad6c8f259fef8fb197f5 9079 
glibc_2.38-7.dsc
 1d7dd6802c2a78ff50f7a8aa79067ae1081155c9b3171d8e2039476a8616d3cd 426224 
glibc_2.38-7.debian.tar.xz
 501648aa333d2048c6dce876f1ea9f03b5fe310735464f6ed2993fde48e00801 10084 
glibc_2.38-7_source.buildinfo
Files:
 3ffb062ca0e88582038d77fbaa0d98ba 9079 libs required glibc_2.38-7.dsc
 207b40287d121674fd6707851b2be8bd 426224 libs required 
glibc_2.38-7.debian.tar.xz
 3939cc96d5c92f172460d89b93ae3414 10084 libs required 
glibc_2.38-7_source.buildinfo

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

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmY1Qa0ACgkQE4jA+Jno
M2u12w/+Pnh2gbWexgiheQpqT181/reyhWCRcg2QPP1nvfufcT0hdDzKVR6h6HX7
zXSFyPwBhVArop4CksPY0jx/aG47Qov/zCqUr6rJyjl6cd+iXXuhQghI2rYGwITd
T1lULA9FzuLZWc2+AztZIfMqPj7yIrydQVBGcxBKYqdTIJhlb4t3BV8ipaJHzutf
M3TOOYT0pMlliaTYUalpmH0FRGFp7VeZ0mxVdPjjOBBOlh1YChC7cqxg87Fjwjfn
Y+ATfK+zxjJDLDPnVTCDums7KnhxPiSOvxpQcWfhkXMyk/myOdgeRv6KyeXNuQOB
8pTMsra12hgtk/6XTp+M3SLULMyNfIgnIfXKAHiCma1Fa/v7+h7ps26rDbV13c9E
W4wCh5RAwuO+IKLiUagNzSReVY67j9R13KkUeJEkt5/b5QKl+sn0OQkdgVVy1oU/
jEpV+f5d1W5JYi4q9AhJCVOlCtCNgtmYNMeKaJQ/qBm8PwHTlTmR0puqf63xET+R
QVlUEg/s+wP+YxZ7lryzQrM6xuPLFc+PhepVv3MNY28q981ZKlEmLnX40Ed5TYMR
nsWHqoOh2E+Oc8MwF3D254EqN3lkPWxTytigrGqRz6++QDp9MJcQgA6w8vcIM3qt
q4394W1X007OwLvDX5df+iGsTh3Bpg+fCVOeKcLHlCOm18HkVqQ=
=0anT
-----END PGP SIGNATURE-----

Attachment: pgpkJzzco6Y6a.pgp
Description: PGP signature


--- End Message ---

Reply via email to