From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>,
Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Cc: Bo YU <tsu.yubo@gmail.com>
Subject: Re: [PATCH] io: Fix record locking contants on 32 bit arch with 64 bit default time_t (BZ#30477)
Date: Thu, 25 May 2023 09:17:42 -0300 [thread overview]
Message-ID: <513b787a-b602-2e6f-2f04-e3e928902081@linaro.org> (raw)
In-Reply-To: <874jo0okyk.fsf@oldenburg.str.redhat.com>
On 25/05/23 05:48, Florian Weimer wrote:
> * Adhemerval Zanella via Libc-alpha:
>
>> diff --git a/sysdeps/unix/sysv/linux/bits/fcntl-linux.h b/sysdeps/unix/sysv/linux/bits/fcntl-linux.h
>> index ca6a0d7516..3c15625599 100644
>> --- a/sysdeps/unix/sysv/linux/bits/fcntl-linux.h
>> +++ b/sysdeps/unix/sysv/linux/bits/fcntl-linux.h
>> @@ -101,7 +101,7 @@
>> #endif
>>
>> #ifndef F_GETLK
>> -# ifndef __USE_FILE_OFFSET64
>> +# if !defined(__USE_FILE_OFFSET64) && __TIMESIZE != 64
>> # define F_GETLK 5 /* Get record locking info. */
>> # define F_SETLK 6 /* Set record locking info (non-blocking). */
>> # define F_SETLKW 7 /* Set record locking info (blocking). */
>
> We have a similar construct in many installed headers. Is this really
> the only place that needs changing?
I did a quick check on the installed headers:
/usr/include/aio.h It conditionalizes the existence of a pad after aio_offset,
and it will create a zero size array in this case. Not ideal,
but this is not strictly an issue.
It also defined whether to redirect to the LFS variants (which
are all aliases)
/usr/include/bits/struct_stat.h It is handled by each architecture and the generic should
be fixed by 7a6ca82f8007ddbd43e2b8fce806ba7101ee47f5.
/usr/include/fcntl.h
/usr/include/stdio.h
/usr/include/sys/mman.h
/usr/include/fcntl.h
/usr/include/sys/types.h
/usr/include/sys/stat.h
/usr/include/dirent.h Define types that change size for LFS, which should not matter
since in this case they are essentially the same; and whether
to redirect to the LFS variants (which also should not matter
since they are aliases).
/usr/include/bits/unistd.h
/usr/include/fts.h
/usr/include/ftw.h
/usr/include/sys/resource.h
/usr/include/sys/sendfile.h
/usr/include/sys/statfs.h
/usr/include/sys/statvfs.h
/usr/include/bits/fcntl-linux.h
/usr/include/bits/fcntl2.h
/usr/include/stdlib.h
/usr/include/glob.h Define whether to redirect to the LFS variants (which are
all aliases).
So it does seems that this is the missing spot of kernel interface that is
changed whether LFS is used or not.
next prev parent reply other threads:[~2023-05-25 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 19:31 Adhemerval Zanella
2023-05-25 8:48 ` Florian Weimer
2023-05-25 12:17 ` Adhemerval Zanella Netto [this message]
2023-05-25 9:00 ` Andreas Schwab
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=513b787a-b602-2e6f-2f04-e3e928902081@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=tsu.yubo@gmail.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).