Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp958805ybl; Wed, 28 Aug 2019 07:43:45 -0700 (PDT) X-Google-Smtp-Source: APXvYqxeLclgENKEkmQEinoRV2a2PhjZG1t+cL+SiJDWWlss0oVXp7uOJbGJKThCK7pxZXoAcH5F X-Received: by 2002:a62:34c4:: with SMTP id b187mr5183924pfa.161.1567003424924; Wed, 28 Aug 2019 07:43:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567003424; cv=none; d=google.com; s=arc-20160816; b=zDGKXNMUl7/pJrTs2C+lhNCdJAfzs+Ttemn0vpPRsMUtOKkZcLy+u6jAwgvg/TEzSB mOwIUHdPMm9KGFq0b4SD9dAHrnhzw2OUbfxRK0YoGT45LJMPkXXZfirwUdbmITFDWmLK cdpEO/Pw/LgeQw7B7QQ0ZeM5fhFSW6q7lPz+WmFyJUfajavy9jZHZABKbR59b/U/GNdI 2jhOLxsKdk4H4YJf3C16hhGNHRLOykRiDejaCpFG4tfzylkQFYjNCwiARjx98oW7YViF o6F9QsNmqp0n0tWTGtw0l2CaDWjR0Xah/8RBAv3e3YmETbeu/sXVbssniIcp6ons3Pbo Sthw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=xI4fjEQ9QR1GChZYEulu4XyBPV7sdzbZDeRuIoXhaWg=; b=xuNwePubyhbEC+2YKtvFh1Kro1ysq5tJiDmg94UkD7ybk2bmz+rCNQsLbBw7i1gA2e D5bXUIdvs+3VoAedFcO/R/F2nBbM1MO4nVpCZZD2uQGvmTzSzkBn2Xn9yFGSWZm59TUE yOUuEjf0BrMtsSB8fkjuaOpE61L3ReJIcV922wou29P3oF4jJQU9O3FGANLfc7B0OfSk H1c7RyCqJiCjp7Rfqb5F6IGyPc1y0UTK3DBT4ernvg2yfI5MotLeaqnEPdkvPRfJ7r1c SWwH+ndX1T4VkcrCZNlRo37ZIIbJP6PtYcvF/xqr/0rFi0OFKyIvMdliemM3XaGg59aa ei8w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b30si1976233pla.368.2019.08.28.07.43.28; Wed, 28 Aug 2019 07:43:44 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726833AbfH1OlB (ORCPT + 99 others); Wed, 28 Aug 2019 10:41:01 -0400 Received: from mx2.suse.de ([195.135.220.15]:53714 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726428AbfH1OlB (ORCPT ); Wed, 28 Aug 2019 10:41:01 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id D959CADFE; Wed, 28 Aug 2019 14:40:59 +0000 (UTC) Date: Wed, 28 Aug 2019 16:40:58 +0200 From: Michal =?UTF-8?B?U3VjaMOhbmVr?= To: Nicholas Piggin Cc: linuxppc-dev@lists.ozlabs.org, David Hildenbrand , "Dmitry V. Levin" , Max Filippov , Paul Mackerras , Breno Leitao , Michael Neuling , Firoz Khan , Allison Randal , Joel Stanley , Steven Rostedt , Alexander Viro , Thomas Gleixner , Hari Bathini , Greg Kroah-Hartman , linux-kernel@vger.kernel.org, "Eric W. Biederman" , Andrew Donnellan , linux-fsdevel@vger.kernel.org, Andrew Morton Subject: Re: [PATCH v2 0/4] Disable compat cruft on ppc64le v2 Message-ID: <20190828164058.76a395b8@naga> In-Reply-To: <1566988993.aiyajovdx0.astroid@bobo.none> References: <1566988993.aiyajovdx0.astroid@bobo.none> X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; x86_64-suse-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 28 Aug 2019 20:57:48 +1000 Nicholas Piggin wrote: > Michal Suchanek's on August 28, 2019 8:30 pm: > > With endian switch disabled by default the ppc64le compat supports > > ppc32le only which is something next to nobody has binaries for. > > > > Less code means less bugs so drop the compat stuff. > > Interesting patches, thanks for looking into it. I don't know much > about compat and wrong endian userspaces. I think sys_switch_endian > is enabled though, it's just a strange fast endian swap thing that > has been disabled by default. > > The first patches look pretty good. Maybe for the last one it could > become a selectable option? That sounds good. > > > > I am not particularly sure about the best way to resolve the llseek > > situation. I don't see anything in the syscal tables making it > > 32bit-only so I suppose it should be available on 64bit as well. > > It's for 32-bit userspace only. Can we just get rid of it, or is > there some old broken 64-bit BE userspace that tries to call it? That sounds like a bug in creating these unified syscall tables then. On architectures that have split tables the 64bit ones do not have llseek. On architectures with one table the syscall is marked as common. Thanks Michal