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=-5.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no 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 DDCAAC433B4 for ; Tue, 13 Apr 2021 15:46:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C235A61353 for ; Tue, 13 Apr 2021 15:46:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S245321AbhDMPrM (ORCPT ); Tue, 13 Apr 2021 11:47:12 -0400 Received: from verein.lst.de ([213.95.11.211]:55281 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237575AbhDMPrJ (ORCPT ); Tue, 13 Apr 2021 11:47:09 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id C892567373; Tue, 13 Apr 2021 17:46:46 +0200 (CEST) Date: Tue, 13 Apr 2021 17:46:46 +0200 From: Christoph Hellwig To: Helge Deller Cc: Christoph Hellwig , Catalin Marinas , Will Deacon , Thomas Bogendoerfer , "James E.J. Bottomley" , Heiko Carstens , Vasily Gorbik , Christian Borntraeger , "David S. Miller" , Arnd Bergmann , linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org Subject: Re: [PATCH 4/5] uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in fcntl.h Message-ID: <20210413154646.GC27287@lst.de> References: <20210412085545.2595431-1-hch@lst.de> <20210412085545.2595431-5-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 13, 2021 at 05:43:18PM +0200, Helge Deller wrote: > On 4/12/21 10:55 AM, Christoph Hellwig wrote: >> The F_GETLK64/F_SETLK64/F_SETLKW64 commands are only implemented for >> 32-bit syscall APIs, but we also need them for compat handling on 64-bit >> kernels. > > Ok. > >> Given that redefining them is rather error prone, as shown by parisc >> getting the opcodes wrong currently, just use the existing definitions >> for the compat handling. > > Can you please show me where parisc gets it currently wrong? > I'm somehow blind to see it and of course I'd like to fix it in > stable kernel series if that's true... Looking again I think my comment was wrong, I thought parisc would fall back to the asm-generic version with different code points for the compat case, but parisc actually already defines the constants unconditionally like this patch does for everyone else. So I'll retract that part of the comment.