From: Petr Vorel <petr.vorel@gmail.com>
To: musl@lists.openwall.com
Subject: Re: [PATCH 1/2] define daddr_t type
Date: Fri, 7 Jun 2019 08:06:20 +0200 [thread overview]
Message-ID: <20190607060619.GD7177@x230> (raw)
In-Reply-To: <20190607055849.GR1506@brightrain.aerifal.cx>
Hi Rich,
> > ....
> > > > +++ b/include/sys/types.h
> > > > @@ -29,6 +29,7 @@ extern "C" {
> > > > #define __NEED_clock_t
> > > > #define __NEED_suseconds_t
> > > > #define __NEED_blksize_t
> > > > +#define __NEED_daddr_t
> > ....
> > > daddr_t is not a standard type, so can't be exposed by default here
> > > (aside from the dubious "*_t is always reserved" rule), and it's only
> > So should it be wrapped by #if defined(_GNU_SOURCE) || defined(_BSD_SOURCE) ?
> > > proposed to be used in one header, so it doesn't belong in alltypes.h
> > > either.
> > Where should it be then? Shell I create bits/types.h for it?
> > The goal is to be loadable from <sys/types.h>
> Why? It's not a reasonable type for any application to use -- we've
> never gotten a report that something failed to build because of its
> absence, and even if we did, it would almost surely be a case of "fix
> the application". It looks like the only reason you wanted it was to
> fix the type of a field in an mtio structure, and in that case the
> type would just need to be defined in mtio.h.
I need it for LTP [1]. It's actually workaround for missing struct ustat [2].
If it's really useless to have it in musl, I'll use in LTP __kernel_daddr_t from <linux/types.h>.
[1] https://patchwork.ozlabs.org/patch/1102380/
[2] https://github.com/linux-test-project/ltp/blob/master/include/lapi/ustat.h
> Rich
Kind regards,
Petr
next prev parent reply other threads:[~2019-06-07 6:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 5:14 Petr Vorel
2019-06-07 5:14 ` [PATCH 2/2] define mt_fileno and mt_fileno struct mtget members as mt_blkno Petr Vorel
2019-06-07 5:31 ` Rich Felker
2019-06-07 5:42 ` Petr Vorel
2019-06-07 5:50 ` Rich Felker
2019-06-07 5:58 ` Petr Vorel
2019-06-07 6:01 ` Rich Felker
2019-06-07 5:28 ` [PATCH 1/2] define daddr_t type Rich Felker
2019-06-07 5:53 ` Petr Vorel
2019-06-07 5:58 ` Rich Felker
2019-06-07 6:06 ` Petr Vorel [this message]
2019-06-07 6:18 ` Rich Felker
2019-06-07 6:28 ` Petr Vorel
2019-06-07 7:22 ` Florian Weimer
2019-06-07 7:48 ` Petr Vorel
2019-06-07 9:21 ` Petr Vorel
2019-06-07 12:52 ` Leah Neukirchen
2019-06-07 15:25 ` Rich Felker
2019-06-10 20:30 ` Rich Felker
2019-06-07 20:57 ` Petr Vorel
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=20190607060619.GD7177@x230 \
--to=petr.vorel@gmail.com \
--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).