From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Lukasz Majewski <lukma@denx.de>
Cc: Joseph Myers <joseph@codesourcery.com>,
Paul Eggert <eggert@cs.ucla.edu>,
Alistair Francis <alistair23@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Alistair Francis <alistair.francis@wdc.com>,
GNU C Library <libc-alpha@sourceware.org>,
Florian Weimer <fweimer@redhat.com>,
Carlos O'Donell <carlos@redhat.com>,
Stepan Golosunov <stepan@golosunov.pp.ru>,
Andreas Schwab <schwab@suse.de>, Zack Weinberg <zackw@panix.com>
Subject: Re: [PATCH] y2038: Reorder placement of st_ino in struct __stat64_t64
Date: Wed, 14 Oct 2020 11:23:25 -0300 [thread overview]
Message-ID: <0733452c-4b8e-d3bf-f522-624dc0e2dc94@linaro.org> (raw)
In-Reply-To: <20201014161428.76862be4@jawa>
On 14/10/2020 11:14, Lukasz Majewski wrote:
> Hi Adhemerval,
>
>> On 14/10/2020 10:00, Lukasz Majewski wrote:
>>> In the installed struct stat{64} the __ino64_t st_ino member is
>>> placed in the end. This patch moves it to the same position as in
>>> the aforementioned, exported structures as it allows less #ifdefs
>>> for __USE_TIME_BITS64 support use case.
>>
>> Why exactly this is required? Afaik this is glibc defined type not
>> currently only used internally and all member accesses are set
>> directly (no use or memcpy or offsetof). Is this related to the
>> issue you saw on the arm environment?
>
> This is required to make the minimal changes to provide -D_TIME_SIZE=64
> support for {f}stat{at} as in:
> https://github.com/lmajewski/y2038_glibc/commit/26aa2ac07246682a505d85dac1c269689964b79b
But the idea it to decouple y2038 stat from the generic stat which
support non-LFS and make it support solely LFS. As Joseph has pointed
out, the __stat64_t64 should be architecture-independent and I think
it simplifies its definition to untie from struct_stat.h (which
has multiple definitions due historically each architecture
to tie with the selected kernel ABI).
It leads to define the struct __stat64_t64 on its own header instead
of trying to accommodate it on stat.h header. The idea it to eventually
export struct_stat_time64.h as an installed header and make the
required redirections on stat.h header for -D_TIME_SIZE=64 (so
stat64 redirects to __stat_time64).
next prev parent reply other threads:[~2020-10-14 14:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 13:00 Lukasz Majewski
2020-10-14 13:13 ` Adhemerval Zanella
2020-10-14 14:14 ` Lukasz Majewski
2020-10-14 14:21 ` Andreas Schwab
2020-10-14 15:33 ` Lukasz Majewski
2020-10-15 10:28 ` Andreas Schwab
2020-10-14 14:23 ` Adhemerval Zanella [this message]
2020-10-14 15:56 ` Lukasz Majewski
2020-10-14 17:50 ` Adhemerval Zanella
2020-10-14 22:00 ` Lukasz Majewski
2020-10-15 11:03 ` Adhemerval Zanella
2020-10-15 11:21 ` Lukasz Majewski
2020-10-14 21:37 ` Joseph Myers
2020-10-15 9:58 ` Lukasz Majewski
2020-10-15 13:04 ` Joseph Myers
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=0733452c-4b8e-d3bf-f522-624dc0e2dc94@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=arnd@arndb.de \
--cc=carlos@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=lukma@denx.de \
--cc=schwab@suse.de \
--cc=stepan@golosunov.pp.ru \
--cc=zackw@panix.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).