From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D3B8FC2F421 for ; Mon, 21 Jan 2019 16:31:28 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AE2F521019 for ; Mon, 21 Jan 2019 16:31:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730577AbfAUQbV (ORCPT ); Mon, 21 Jan 2019 11:31:21 -0500 Received: from mail-qt1-f193.google.com ([209.85.160.193]:44211 "EHLO mail-qt1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730112AbfAUQbU (ORCPT ); Mon, 21 Jan 2019 11:31:20 -0500 Received: by mail-qt1-f193.google.com with SMTP id n32so24127341qte.11; Mon, 21 Jan 2019 08:31:19 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ugnN37Htp2pcGbvXPo+DEz/r4541Rca2swp85kVj/dg=; b=AN4J5uEie5Hx6iRzpgTqk2T78/TYbZGWKu5NP3ScooQUyeF+pmyzaxewwf+GzaK+uP nYxvf88tBZStbUoK/Lpu2lZTijjAkRYgGZdTml5XNBvpxoa8v7N78Gc64UoRdsFOM4eV 92y+zLsPd9e7Vb0DeQ8153pnjbQ4v9+wUCBTLieS5wVDIHNRqZslR8xxxmdMciaITTjG QjZy8xIFdXDUdFOTyMMhQoc6kIUZ4QUoVLQIfpJBEdRRD6IcpD1CZs4f87OjXnqL5hO1 fut8e9AbtYZy8M3vl2AkJoriRYJIB6vvIV0Ob/+TXIQThjD5KPlZZBzy3BNJO5njSqKk IW/g== X-Gm-Message-State: AJcUukdhC7yC2jcZZEZAx/kA2Af/xMeH3SmcxCgjRSzE7Bk8qsfTVphi yFeYy2ypdj+52BDoVBK+QEffrKZNQpm0NdOBih0= X-Google-Smtp-Source: ALg8bN4IjC8153m9pB3iBWOATh3R/RnsAQ6wVGb5LY7XqftLLWs9CXLGl7GxR+zlIVcd8dP96h71Ls+Fr/txo5y0uPg= X-Received: by 2002:aed:35c5:: with SMTP id d5mr27326381qte.212.1548088278474; Mon, 21 Jan 2019 08:31:18 -0800 (PST) MIME-Version: 1.0 References: <20190118161835.2259170-1-arnd@arndb.de> <20190118161835.2259170-30-arnd@arndb.de> In-Reply-To: <20190118161835.2259170-30-arnd@arndb.de> From: Arnd Bergmann Date: Mon, 21 Jan 2019 17:31:01 +0100 Message-ID: Subject: Re: [PATCH v2 29/29] y2038: add 64-bit time_t syscalls to all 32-bit architectures To: y2038 Mailman List , Linux API , Linux Kernel Mailing List , linux-arch Cc: Matt Turner , Russell King - ARM Linux , Catalin Marinas , Will Deacon , Tony Luck , Fenghua Yu , Geert Uytterhoeven , Michal Simek , Paul Burton , Helge Deller , Benjamin Herrenschmidt , Michael Ellerman , Martin Schwidefsky , Heiko Carstens , Rich Felker , David Miller , Andy Lutomirski , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , "the arch/x86 maintainers" , Max Filippov , Andrew Morton , Deepa Dinamani , "Eric W . Biederman" , Firoz Khan , alpha , Linux ARM , linux-ia64@vger.kernel.org, linux-m68k , linux-mips@vger.kernel.org, Parisc List , linuxppc-dev , linux-s390 , Linux-sh list , sparclinux , Networking , Linux FS-devel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-parisc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-parisc@vger.kernel.org On Fri, Jan 18, 2019 at 5:25 PM Arnd Bergmann wrote: > > This adds 21 new system calls on each ABI that has 32-bit time_t > today. All of these have the exact same semantics as their existing > counterparts, and the new ones all have macro names that end in 'time64' > for clarification. > > This gets us to the point of being able to safely use a C library > that has 64-bit time_t in user space. There are still a couple of > loose ends to tie up in various areas of the code, but this is the > big one, and should be entirely uncontroversial at this point. I've successfully tested this with musl and LTP now, using an i386 kernel. The musl port I used is at https://git.linaro.org/people/arnd.bergmann/musl-y2038.git/ This is just an updated version of what I used for testing last year, using the current syscall assignment, and going back to the time32 versions of getitimer/setitimer and wait4/waitid/getusage. It's certainly not intended for merging like this, but a proper musl port is under discussion now, and this should be sufficient if anyone else wants to try out the new syscall ABI before we merge it. The LTP I have is heavily hacked, and has a number of failures resulting from differences between musl and glibc, or from the way we convert between the kernel types and the user space types. The testing found one minor bug in all the kernel syscall tables: > +418 common mq_timedsend_time64 sys_mq_timedsend > +419 common mq_timedreceiv_time64 sys_mq_timedreceive While this would have fit in with umount(), creat() and mknod(), it was unintentional, and I've changed it back to mq_timedreceive_time64 (with an added 'e'). Arnd