public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "syq at debian dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29730] broken y2038 support in fstatat on MIPS N64
Date: Sat, 29 Oct 2022 19:45:48 +0000	[thread overview]
Message-ID: <bug-29730-131-VDj6iWotmg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29730-131@http.sourceware.org/bugzilla/>

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

--- Comment #5 from YunQiang Su <syq at debian dot org> ---
Ohh, you are right.

For __TIMESIZE == 64 && __WORDSIZE == 32 systems, 
I think that the kernel should provide a setitimer64 syscall.

Currently, for glibc, maybe that we should define a new macro for
these systems:
   #define KERNEL_SETTIMER_IS_32_BIT

and in setitimer.c



#if KERNEL_SETTIMER_IS_32_BIT
  if (! in_int32_t_range (new_value->it_interval.tv_sec)
      || ! in_int32_t_range (new_value->it_value.tv_sec))
#else
  if (! in_time_t_range (new_value->it_interval.tv_sec)
      || ! in_time_t_range (new_value->it_value.tv_sec))
#endif
    {
      __set_errno (EOVERFLOW);
      return -1;
    }


Anyway, we shouldn't confuse the function name.

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

  parent reply	other threads:[~2022-10-29 19:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28 19:39 [Bug libc/29730] New: " aurelien at aurel32 dot net
2022-10-29 16:56 ` [Bug libc/29730] " syq at debian dot org
2022-10-29 17:16 ` syq at debian dot org
2022-10-29 17:28 ` syq at debian dot org
2022-10-29 19:26 ` aurelien at aurel32 dot net
2022-10-29 19:45 ` syq at debian dot org [this message]
2022-10-30  4:14 ` syq at debian dot org
2022-10-30 14:30 ` adhemerval.zanella at linaro dot org
2022-10-30 16:55 ` syq at debian dot org
2022-10-30 18:07 ` aurelien at aurel32 dot net
2022-10-30 18:24 ` adhemerval.zanella at linaro dot org
2022-10-31  0:53 ` syq at debian dot org
2022-10-31  2:48 ` syq at debian dot org
2022-10-31  4:01 ` syq at debian dot org
2022-10-31  5:11 ` syq at debian dot org
2022-10-31 13:17 ` adhemerval.zanella at linaro dot org
2022-10-31 13:54 ` adhemerval.zanella at linaro dot org
2022-10-31 16:07 ` adhemerval.zanella at linaro dot org
2022-10-31 17:01 ` syq at debian dot org
2022-10-31 17:14 ` syq at debian dot org
2022-10-31 17:28 ` adhemerval.zanella at linaro dot org
2022-10-31 17:29 ` adhemerval.zanella at linaro dot org
2022-11-01 12:11 ` aurelien at aurel32 dot net
2022-11-01 12:11 ` aurelien at aurel32 dot net
2022-11-02 15:37 ` aurelien at aurel32 dot net
2022-11-02 15:39 ` cvs-commit at gcc dot gnu.org
2022-11-02 16:35 ` cvs-commit at gcc dot gnu.org
2022-11-02 18:12 ` cvs-commit at gcc dot gnu.org
2022-11-04  1:56 ` syq at debian dot org

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-29730-131-VDj6iWotmg@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).