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] New: lchmod test fails after 2038 on 32 bits systems
Date: Fri, 10 Feb 2023 09:44:37 +0000	[thread overview]
Message-ID: <bug-30111-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 30111
           Summary: lchmod test fails after 2038 on 32 bits systems
           Product: glibc
           Version: 2.35
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: time
          Assignee: unassigned at sourceware dot org
          Reporter: blemouzy at centralp dot fr
  Target Milestone: ---

Environment
===========

- i.MX6 32 bits CPU
- Yocto Kirkstone (kirkstone-4.0.6)
- Linux 5.10.109
- glibc 2.35 (8d125a1f9145ad90c94e438858d6b5b7578686f2)
- RFS built with "-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" flags
- System date set after 011903142038 (2038 Jan 19 03:14:00)

Description
===========

tst-lchmod-time64 returns after 2038:

    error: support_descriptors.c:103: readdir: fstat64 (0) failed: Value too
large for defined data type
    error: 1 test failures

tst-lchmod-time64 returns before 2038:

    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

Please find associated strace attached.

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

             reply	other threads:[~2023-02-10  9:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10  9:44 blemouzy at centralp dot fr [this message]
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
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@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).