public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "blemouzy at centralp dot fr" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug time/30111] support_descriptors_list fails after 2038 on 32 bits systems
Date: Tue, 12 Mar 2024 07:34:09 +0000	[thread overview]
Message-ID: <bug-30111-131-yFGnB9ZC6m@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30111-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30111

--- Comment #5 from LEMOUZY Benjamin <blemouzy at centralp dot fr> ---
Hello,

As
https://sourceware.org/git/?p=glibc.git;a=commit;h=3bfdc4e2bceb601b90c81a9baa73c1904db58b2f
has not been backported to release/2.35/master, I did it myself.

But I still have the issue:

  # date
  Tue Mar 12 06:53:05 UTC 2024
  # /usr/lib/glibc-tests/ptest/tests/glibc-ptest/tst-lchmod-time64
  info: testing lchmod
  info: testing fchmodat with AT_FDCWD
  info: testing fchmodat with relative path
  info: re-running tests (after trying to empty /proc)
  info: testing lchmod
  info: testing fchmodat with AT_FDCWD
  info: testing fchmodat with relative path


  # date
  Thu Jan 19 03:14:02 UTC 2040
  # /usr/lib/glibc-tests/ptest/tests/glibc-ptest/tst-lchmod-time64
  error: support_descriptors.c:103: readdir: fstat64 (0) failed: Value too
large for defined data type
  error: 1 test failures

Do I also need to backport another commits to fix it in 2.35?
(new strace outputs attached)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-03-12  7:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10  9:44 [Bug time/30111] New: lchmod test " blemouzy at centralp dot fr
2023-02-10  9:45 ` [Bug time/30111] " blemouzy at centralp dot fr
2023-02-10  9:45 ` blemouzy at centralp dot fr
2023-02-23 12:31 ` [Bug time/30111] support_descriptors_list " schwab@linux-m68k.org
2023-03-02 12:06 ` schwab@linux-m68k.org
2024-03-12  7:34 ` blemouzy at centralp dot fr [this message]
2024-03-12  7:35 ` blemouzy at centralp dot fr
2024-03-12  7:35 ` blemouzy at centralp dot fr
2024-03-12 19:33 ` adhemerval.zanella at linaro dot org
2024-03-13  9:15 ` blemouzy at centralp dot fr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-30111-131-yFGnB9ZC6m@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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 read-only IMAP folder(s) and NNTP newsgroup(s).