This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH v3 2/5] y2038: Introduce internal for glibc struct __timespec64
- From: Andreas Schwab <schwab at suse dot de>
- To: Lukasz Majewski <lukma at denx dot de>
- Cc: libc-alpha at sourceware dot org, Stepan Golosunov <stepan at golosunov dot pp dot ru>, Arnd Bergmann <arnd at arndb dot de>, Paul Eggert <eggert at cs dot ucla dot edu>, Joseph Myers <joseph at codesourcery dot com>
- Date: Wed, 08 May 2019 10:38:20 +0200
- Subject: Re: [PATCH v3 2/5] y2038: Introduce internal for glibc struct __timespec64
- References: <20190414220841.20243-1-lukma@denx.de> <20190507131848.30980-1-lukma@denx.de> <20190507131848.30980-3-lukma@denx.de> <mvmv9ymqtnj.fsf@suse.de> <20190507160736.147b31a8@jawa> <mvmimumqrnr.fsf@suse.de> <20190508103202.10465eed@jawa>
On Mai 08 2019, Lukasz Majewski <lukma@denx.de> wrote:
> My point is if we do need at any point in time to clear this padding
> (due to e.g. kernel bug when passing data to syscalls [2] or solve issue
> as presented in [*]).
Yes, but you don't need to use a *bitfield*.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."