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=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS 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 C428FC1B0F7 for ; Fri, 18 Jan 2019 20:46:14 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id E7AD020896 for ; Fri, 18 Jan 2019 20:46:13 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E7AD020896 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=arndb.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 43hCdv33kRzDrDq for ; Sat, 19 Jan 2019 07:46:11 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=gmail.com (client-ip=209.85.160.194; helo=mail-qt1-f194.google.com; envelope-from=arndbergmann@gmail.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=arndb.de Received: from mail-qt1-f194.google.com (mail-qt1-f194.google.com [209.85.160.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 43hCc33DchzDr94 for ; Sat, 19 Jan 2019 07:44:35 +1100 (AEDT) Received: by mail-qt1-f194.google.com with SMTP id i7so16675199qtj.10 for ; Fri, 18 Jan 2019 12:44:35 -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=ORQ5TPnixziDIHsuvdhJc04sEDyDC/r90DJmiSnzeTU=; b=hoMG5j1Ys1bpcYPD+ICeCgWhYPzx6d2vrulllmZ0bB8Wk80+j2Xy3nyw2uB9Y3gLvM 9yQB2U+9QdL8fwYUOA2zZShB16mK9G3ucT+1rAP6fWs35R7E6wEuooDELWdZHJDIbRf/ kI/dH7dWeLbvc9HGRNmHLc3i/4m0T4TGV5PfWL5QQKbwF+xqFLur/2CPo17tmjFr92Nd ZBdmduNjh38cm1TE3jHVtO39NL8n20qf5VgmbjfM6KvCQAeoz6/fPAMdZ1Vp6brsd/Kv JIzds6B9OXyMNs9B5NzXOeV0HUfy+0ff9wGlljJliuUJTvAPc50TCMkSfuhisnXiZhYZ DA6w== X-Gm-Message-State: AJcUukfkqF36zNXTLjvZ9veqypvsci9qnrWWS/9duSKCTLKrG9WnwvZ2 cwa7rdtcx0Hj6G6X+AG1kxRoxRyvEScha35K1W4= X-Google-Smtp-Source: ALg8bN4ggcJ9u9iUb42HjHwnUQYctSfqKH3E3MdNfQhsEyd2ovYbbCJ8aRRYCcgq2HtqlmRxO9eWK6dWZp4WMFrZjzM= X-Received: by 2002:a0c:d992:: with SMTP id y18mr17616058qvj.161.1547844273008; Fri, 18 Jan 2019 12:44:33 -0800 (PST) MIME-Version: 1.0 References: <20190118161835.2259170-1-arnd@arndb.de> <20190118161835.2259170-30-arnd@arndb.de> In-Reply-To: From: Arnd Bergmann Date: Fri, 18 Jan 2019 21:44:16 +0100 Message-ID: Subject: Re: [PATCH v2 29/29] y2038: add 64-bit time_t syscalls to all 32-bit architectures To: Andy Lutomirski Content-Type: text/plain; charset="UTF-8" X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Rich Felker , linux-ia64@vger.kernel.org, Linux-sh list , Heiko Carstens , linux-mips@vger.kernel.org, Max Filippov , Network Development , Deepa Dinamani , "H. Peter Anvin" , sparclinux , linux-arch , linux-s390 , y2038 Mailman List , Helge Deller , X86 ML , Russell King , Ingo Molnar , Geert Uytterhoeven , Catalin Marinas , Firoz Khan , Matt Turner , Fenghua Yu , Will Deacon , Linux FS Devel , linux-m68k , Thomas Gleixner , linux-arm-kernel , Michal Simek , Tony Luck , Parisc List , Linux API , LKML , Paul Burton , "Eric W. Biederman" , alpha , Martin Schwidefsky , Andrew Morton , linuxppc-dev , "David S. Miller" Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Fri, Jan 18, 2019 at 8:53 PM Andy Lutomirski wrote: > I think we have two issues if we reuse those numbers for new syscalls. > First, I'd really like to see new syscalls be numbered consistently > everywhere, or at least on all x86 variants, and we can't on x32 > because they mean something else. Perhaps more importantly, due to > what is arguably a rather severe bug, issuing a native x86_64 syscall > (x32 bit clear) with nr in the range 512..547 does *not* return > -ENOSYS on a kernel with x32 enabled. Instead it does something that > is somewhat arbitrary. With my patch applied, it will return -ENOSYS, > but old kernels will still exist, and this will break syscall probing. > > Can we perhaps just start the consistent numbers above 547 or maybe > block out 512..547 in the new regime? I'm definitely fine with not reusing them ever, and jumping from 511 to 548 when we get there on all architectures, if you think that helps. While we could also jump to 548 *now*, I think that would be a bit wasteful. Syscall numbers are fairly cheap, but not entirely free, especially when you consider architectures like mips that have an upper bound of 1000 syscalls before they have to get inventive. Arnd