mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Thorsten Glaser <tg@mirbsd.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: klibc@zytor.com, libc-alpha@sourceware.org,
	y2038@lists.linaro.org, linux-api@vger.kernel.org,
	musl@lists.openwall.com, linux-kernel@vger.kernel.org,
	Rich Felker <dalias@libc.org>,
	cferris@google.com, enh@google.com,
	"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: [klibc] kernel/libc uapi changes for y2038
Date: Mon, 18 May 2015 12:16:48 +0000 (UTC)	[thread overview]
Message-ID: <Pine.BSM.4.64L.1505181214530.8249@herc.mirbsd.org> (raw)
In-Reply-To: <2664016.bYZKg6FQqR@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
_______________________________________________
Y2038 mailing list
Y2038@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/y2038

  reply	other threads:[~2015-05-18 12:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18  9:53 Arnd Bergmann
2015-05-18 12:16 ` Thorsten Glaser [this message]
2015-05-18 13:32   ` [Y2038] [klibc] " Arnd Bergmann
2015-05-18 17:03     ` Thorsten Glaser
2015-05-18 20:35       ` Arnd Bergmann
2015-05-19 17:54 ` [Y2038] " John Stultz
2015-05-27 15:28 ` [klibc] " H. Peter Anvin
     [not found]   ` <5565E2AC.3070306-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2015-05-27 20:19     ` Arnd Bergmann

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=Pine.BSM.4.64L.1505181214530.8249@herc.mirbsd.org \
    --to=tg@mirbsd.de \
    --cc=arnd@arndb.de \
    --cc=cferris@google.com \
    --cc=dalias@libc.org \
    --cc=enh@google.com \
    --cc=joseph@codesourcery.com \
    --cc=klibc@zytor.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=musl@lists.openwall.com \
    --cc=y2038@lists.linaro.org \
    /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).