From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: loff_t definition in <fcntl.h> (vs. glibc in <sys/types.h>)
Date: Thu, 17 Oct 2019 21:21:18 -0400 [thread overview]
Message-ID: <20191018012118.GV16318@brightrain.aerifal.cx> (raw)
In-Reply-To: <20191017225203.GA9969@x230>
On Fri, Oct 18, 2019 at 12:52:05AM +0200, Petr Vorel wrote:
> Hi Rich,
>
> > > what is the reason for loff_t being defined in <fcntl.h> ?
> > > It was defined some time ago, in v0.9.5.
>
> > > glibc (and thus uclibc; + also Bionic) has it in <sys/types.h>, defined long
> > > time before. Who is correct? I guess loff_t not being posix, therefore it
> > > shouldn't be in <sys/types.h> ?
>
> > > I'm asking because it'd be nice to have it for both in single header
> > > (portability).
>
> > The reason it's defined in fcntl.h is because that's where the
> > declarations for the only functions which use it in their interfaces
> > reside. If it needs to be made available from multiple places, that
> > could be done at some point, but this is a really minor type that
> > shouldn't be used except with with functions defined in terms of it.
> Thanks for info. So maybe glibc shouldn't have defined it in <sys/types.h>.
>
> FYI I'm handling compatibility issues for LTP [1], which often uses kernel API
> in order to test it. Probably normal user space applications don't have needs we
> have in LTP.
What did you encounter that needs it that's not declared in fcntl.h?
Are you sure you're not using loff_t where off_t would be the right
type? loff_t only appears in some kernel interfaces that were intended
to work the same regardless of whether glibc was configured for 32-bit
or 64-bit off_t.
Rich
prev parent reply other threads:[~2019-10-18 1:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 21:28 Petr Vorel
2019-10-16 21:53 ` Rich Felker
2019-10-17 22:52 ` Petr Vorel
2019-10-18 1:21 ` Rich Felker [this message]
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=20191018012118.GV16318@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).