This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [klibc] kernel/libc uapi changes for y2038
- From: Thorsten Glaser <tg at mirbsd dot de>
- To: Arnd Bergmann <arnd at arndb dot de>
- Cc: linux-api at vger dot kernel dot org, klibc at zytor dot com, libc-alpha at sourceware dot org, y2038 at lists dot linaro dot org, musl at lists dot openwall dot com, linux-kernel at vger dot kernel dot org, Rich Felker <dalias at libc dot org>, cferris at google dot com, enh at google dot com, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Mon, 18 May 2015 12:16:48 +0000 (UTC)
- Subject: Re: [klibc] kernel/libc uapi changes for y2038
- Authentication-results: sourceware.org; auth=none
- References: <2664016 dot bYZKg6FQqR at wuerfel>
Arnd Bergmann dixit:
>In the patch series I posted recently [1], I introduce new system calls to deal
>with modified data structures, but left the question open on how these should
>be best accessed from libc. The patches introduce a new __kernel_time64_t type
Can we please have ioctls fixed for mixed 32/64-bit systems
such as MIPS (o32/n32/n64) and x86 (i386/x32/amd64) first,
before even more such chance for breakage is introduced?
I still need to use an amd64 chroot on my x32 system to do
things such as set up iptables, because those ioctls break,
because they contain data structures that contain, well,
time types. Your proposal has a nÅn-zero chance to bring
these issues to i386 (and other architectures).
Thanks,
//mirabilos
--
<ch> you introduced a merge commit â<mika> % g rebase -i HEAD^^
<mika> sorry, no idea and rebasing just fscked â<mika> Segmentation
<ch> should have cloned into a clean repo â fault (core dumped)
<ch> if I rebase that now, it's really ugh â<mika:#grml> wuahhhhhh