Received: by 2002:a05:6a10:7420:0:0:0:0 with SMTP id hk32csp1119293pxb; Wed, 16 Feb 2022 11:27:51 -0800 (PST) X-Google-Smtp-Source: ABdhPJzOk70wbJMmnvQKRWXyp0bYHVto4GiAhRnC2ldF2uDcstPl2v6iwDmtVsUJGE2/2Y6Xmya5 X-Received: by 2002:a17:903:2c5:b0:14f:4a29:1f64 with SMTP id s5-20020a17090302c500b0014f4a291f64mr3455695plk.90.1645039670870; Wed, 16 Feb 2022 11:27:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645039670; cv=none; d=google.com; s=arc-20160816; b=qrP9GOyfvnIoOtiyGvNm7r002cIeUfG4LpesErxGdrUGdHUWzs9KGVveq/csyKy4u/ SoMnfDOYt1+7TgK12DdNQp6+CDQ76x8dlxnVsYeHbbSj/apchA0zqA70e30uehZJs6vS ou4/K5X5W3788M2KgI2xDg2q5+ZnyHiRXPfjODdlvArMAMdNPYmvAOD244W2C6W5A3c1 8WlrqLQGIyQFrAUf60X/BjdLrXjCgYaHx6b/xIm9aP/cQ5TrfIL29kLG9G0L30EhTW2z 4N9SgVgkd8Wsh/tW3STVLJyEGlcHjJD80xCBDRFqF6n+eOHNS7gYfo5f221wqbG1HSrS LLOA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=JnYwwuDXh6roNT1x6wXviF81exsv2Q/AEzJ6y2PLPrI=; b=A41BI0FhsMCZO6LZfPU3nPNiyyPdsJH9jqbb94eKFpZy9FxwkEGInO+PaGLaWP7Ho0 +tMlWWQdb9PvJkhvHXaP8zAQzGpPDQEii6oIoncSSiKuHnZuEQWkoi1Fx4dtI3HUE2mV oNPD7SsecaoS2NAy5AsgtSXVq/cprdQg9QjogPbpXFlSq4BjdlyJhwGbtcvWqaiaHb7J s23xX+sFn0RLp/bdW9WB2hyzPzZACoVy/046I3ChQaZzcJKzSOLwEhaLOE+iSkP8aiTe WAI+b1K/wEEP7e48fm7GIqCYDuyvrCTMhdJsN642OyA/fV0fYPxnyBQ9eAVyTIiuJQzg +DtQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m1si8656421pgu.401.2022.02.16.11.27.34; Wed, 16 Feb 2022 11:27:50 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237739AbiBPSld (ORCPT + 99 others); Wed, 16 Feb 2022 13:41:33 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:51640 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237734AbiBPSl3 (ORCPT ); Wed, 16 Feb 2022 13:41:29 -0500 Received: from mx2.smtp.larsendata.com (mx2.smtp.larsendata.com [91.221.196.228]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DE7782AF3D1 for ; Wed, 16 Feb 2022 10:41:15 -0800 (PST) Received: from mail01.mxhotel.dk (mail01.mxhotel.dk [91.221.196.236]) by mx2.smtp.larsendata.com (Halon) with ESMTPS id 0f791715-8f58-11ec-b2df-0050568cd888; Wed, 16 Feb 2022 18:41:32 +0000 (UTC) Received: from ravnborg.org (80-162-45-141-cable.dk.customer.tdc.net [80.162.45.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: sam@ravnborg.org) by mail01.mxhotel.dk (Postfix) with ESMTPSA id B2BEB194B1C; Wed, 16 Feb 2022 19:41:12 +0100 (CET) Date: Wed, 16 Feb 2022 19:41:09 +0100 X-Report-Abuse-To: abuse@mxhotel.dk From: Sam Ravnborg To: Arnd Bergmann Cc: Linus Torvalds , Christoph Hellwig , linux-arch@vger.kernel.org, linux-mm@kvack.org, linux-api@vger.kernel.org, arnd@arndb.de, linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk, linux@armlinux.org.uk, will@kernel.org, guoren@kernel.org, bcain@codeaurora.org, geert@linux-m68k.org, monstr@monstr.eu, tsbogend@alpha.franken.de, nickhu@andestech.com, green.hu@gmail.com, dinguyen@kernel.org, shorne@gmail.com, deller@gmx.de, mpe@ellerman.id.au, peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com, hca@linux.ibm.com, dalias@libc.org, davem@davemloft.net, richard@nod.at, x86@kernel.org, jcmvbkbc@gmail.com, ebiederm@xmission.com, akpm@linux-foundation.org, ardb@kernel.org, linux-alpha@vger.kernel.org, linux-snps-arc@lists.infradead.org, linux-csky@vger.kernel.org, linux-hexagon@vger.kernel.org, linux-ia64@vger.kernel.org, linux-m68k@lists.linux-m68k.org, linux-mips@vger.kernel.org, openrisc@lists.librecores.org, linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linux-um@lists.infradead.org, linux-xtensa@linux-xtensa.org Subject: Re: [PATCH v2 15/18] sparc64: remove CONFIG_SET_FS support Message-ID: References: <20220216131332.1489939-1-arnd@kernel.org> <20220216131332.1489939-16-arnd@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Arnd, On Wed, Feb 16, 2022 at 07:34:59PM +0100, Sam Ravnborg wrote: > Hi Arnd. > > On Wed, Feb 16, 2022 at 02:13:29PM +0100, Arnd Bergmann wrote: > > From: Arnd Bergmann > > > > sparc64 uses address space identifiers to differentiate between kernel > > and user space, using ASI_P for kernel threads but ASI_AIUS for normal > > user space, with the option of changing between them. > > > > As nothing really changes the ASI any more, just hardcode ASI_AIUS > > everywhere. Kernel threads are not allowed to access __user pointers > > anyway. > > > > Signed-off-by: Arnd Bergmann > > --- > > arch/sparc/include/asm/processor_64.h | 4 ---- > > arch/sparc/include/asm/switch_to_64.h | 4 +--- > > arch/sparc/include/asm/thread_info_64.h | 4 +--- > > arch/sparc/include/asm/uaccess_64.h | 20 +------------------- > > arch/sparc/kernel/process_64.c | 12 ------------ > > arch/sparc/kernel/traps_64.c | 2 -- > > arch/sparc/lib/NGmemcpy.S | 3 +-- > > arch/sparc/mm/init_64.c | 7 ++++--- > > 8 files changed, 8 insertions(+), 48 deletions(-) > > I think you somehow missed the Kconfig change, and also the related > sparc32 change which continue to have set_fs() after this patch. I now notice the sparc32 bits are in the last patch. To avoid breaking bisect-ability on sparc64 I think you need to merge the sparc32 changes with this patch, unless the sparc64 changes can coexist with CONFIG_SET_FS continue to be set. Sam