linux-kernel - Re: [klibc] kernel/libc uapi changes for y2038

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.BSM.4.64L.1505181214530.8249@herc.mirbsd.org>
Date:	Mon, 18 May 2015 12:16:48 +0000 (UTC)
From:	Thorsten Glaser <tg@...bsd.de>
To:	Arnd Bergmann <arnd@...db.de>
cc:	linux-api@...r.kernel.org, klibc@...or.com,
	libc-alpha@...rceware.org, y2038@...ts.linaro.org,
	musl@...ts.openwall.com, linux-kernel@...r.kernel.org,
	Rich Felker <dalias@...c.org>, cferris@...gle.com,
	enh@...gle.com, "Joseph S. Myers" <joseph@...esourcery.com>
Subject: Re: [klibc] kernel/libc uapi changes for y2038

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/