unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Adhemerval Zanella Netto" <adhemerval.zanella@linaro.org>,
	"YunQiang Su" <yunqiang.su@cipunited.com>,
	"Xi Ruoyao" <libc-alpha@sourceware.org>
Cc: syq@debian.org, aurelien@aurel32.net,
	"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
	"Maciej W. Rozycki" <macro@orcam.me.uk>
Subject: Re: [PATCH] Rename STAT_HAS_TIME32 to KERNEL_STAT64_HAS_TIME32
Date: Mon, 07 Nov 2022 19:24:58 +0100	[thread overview]
Message-ID: <6100f772-fab4-4e92-a6a9-cf882954df9d@app.fastmail.com> (raw)
In-Reply-To: <a2ceea5d-27a9-6efd-2414-37c807420630@linaro.org>

On Mon, Nov 7, 2022, at 19:08, Adhemerval Zanella Netto wrote:
> On 04/11/22 07:02, Arnd Bergmann wrote:

> In fact it was reported as an y2106 problem some time ago [1] and we
> fixed on 2.34 [2].  And I give that STAT_HAS_TIME32 is not entirely
> clear, since for glibc perspective is has multiple stat definitions.

I think we need to coordinate this when we change the kernel to
add truncation of the 64-bit time values. It sounds like glibc
does an 'unsigned int' to 'long long' conversion for the legacy
stat syscall, rather than a conversion from a signed value, and
it would be helpful to have a matching interpretation between
kernel and glibc.

What is the glibc behavior for i386 with 64-bit time_t on a
kernel without statx? Does that also intepret a time value
of -1u as a 2106 timestamp, or does it convert that into a
1969 timestamp like the other (not mips/pa-risc) 64-bit
architectures do?

      Arnd

  reply	other threads:[~2022-11-07 18:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04  1:54 [PATCH] Rename STAT_HAS_TIME32 to KERNEL_STAT64_HAS_TIME32 YunQiang Su
2022-11-04 10:02 ` Arnd Bergmann
2022-11-07 18:08   ` Adhemerval Zanella Netto via Libc-alpha
2022-11-07 18:24     ` Arnd Bergmann [this message]
2022-11-07 18:45       ` Adhemerval Zanella Netto via Libc-alpha
2022-11-08 11:21         ` Arnd Bergmann
2022-11-08 12:04           ` Adhemerval Zanella Netto via Libc-alpha
2022-11-17 16:47 ` Adhemerval Zanella Netto via Libc-alpha

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

  List information: https://www.gnu.org/software/libc/involved.html

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

  git send-email \
    --in-reply-to=6100f772-fab4-4e92-a6a9-cf882954df9d@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=adhemerval.zanella@linaro.org \
    --cc=aurelien@aurel32.net \
    --cc=jiaxun.yang@flygoat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=macro@orcam.me.uk \
    --cc=syq@debian.org \
    --cc=yunqiang.su@cipunited.com \
    /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).