Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp5673957pxb; Mon, 14 Feb 2022 05:04:52 -0800 (PST) X-Google-Smtp-Source: ABdhPJy7Io8yt8hiVgAXwoFZRRXzsy5hOXde8KaobYIli6yiapn2E4ZNNzGwDesbaNdt03s5zI7Q X-Received: by 2002:a65:5c48:: with SMTP id v8mr11402522pgr.343.1644843892651; Mon, 14 Feb 2022 05:04:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1644843892; cv=none; d=google.com; s=arc-20160816; b=KBG+9KQquzTc8XnpvhRb9/17enPHshP8dTMOeFNsYYBZFAk1o6C6MFchTX7IN35qqI AvTT9U/NwTJ0NaanX83zz3tY+TklH9mzaqZgtVF/yt5+4Ss9WFCrsOhXrJr/LAQNmAsy WZgru9Z2DaYxNJ65QuCnq4FUiiNXjBRatwM2+bVA3Q5JDtbS2ccHdu++AIf4yxdtMDrc Pik8bljo9QMTztyhurZDw5ZpRrtqVlL/IAC1TqmieGTB4feaaV6SoLK07nq0a6kmOiUa L+2yDO6mkOgi6hgfKYLnJhPEr0SC/emYHVdify8tDRZZtUnV3VsdZjXcJWtpelgKbOBX JO4w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:subject:mime-version:message-id:date:user-agent :references:in-reply-to:cc:to:from; bh=g5j4RBbYn1q177ZpYMG+EqQovxjfiQbkW1Lux4AGUFM=; b=TCe5X0u+63TY/Npo0fBYJMGIrVfM7QwHz3fb1f5Y5xIJ1a6SNf9DTCOQezHC3mpIvb R00+7SM9tW7xhAcv5BKFDRPY6z07NhdNaMdjN7RPkjyRXivPFGJ0mzkGUQTzlr9vjBe4 8Da3ll46X6LXVQ3hMHE+FJl3eIcDkUHy5BE4KPEE4pFayY5PeHnMVGSKfpCH8OEYoFB4 YMtl8KIFay+oo3zm4B2F/sh5pmvBLh/92sUoeDO7fpphmkz+ngvSpnry2e1ksT5GT+uK lTW+3Jf9WPiad2/NkSE+eYguW5PRk6DhteQ8KU5Kpkkt0jHr4gIJfmj0U4baIphgqfSJ 6J5g== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=xmission.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id h19si23739771pgj.590.2022.02.14.05.04.40; Mon, 14 Feb 2022 05:04:52 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=xmission.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1353511AbiBKVK0 (ORCPT + 93 others); Fri, 11 Feb 2022 16:10:26 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:38164 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231329AbiBKVKW (ORCPT ); Fri, 11 Feb 2022 16:10:22 -0500 Received: from out03.mta.xmission.com (out03.mta.xmission.com [166.70.13.233]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0B9A4BF7 for ; Fri, 11 Feb 2022 13:10:21 -0800 (PST) Received: from in01.mta.xmission.com ([166.70.13.51]:37100) by out03.mta.xmission.com with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1nIdBK-00E2Bx-SL; Fri, 11 Feb 2022 14:10:18 -0700 Received: from ip68-227-174-4.om.om.cox.net ([68.227.174.4]:53086 helo=email.froward.int.ebiederm.org.xmission.com) by in01.mta.xmission.com with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1nIdBI-001IMe-Qe; Fri, 11 Feb 2022 14:10:18 -0700 From: "Eric W. Biederman" To: Arnd Bergmann Cc: Linus Torvalds , Stafford Horne , Michal Simek , Linux-Arch , LKML , Christoph Hellwig , Al Viro , Arnd Bergmann , Geert Uytterhoeven , "Peter Zijlstra (Intel)" , Catalin Marinas , Mark Rutland In-Reply-To: (Arnd Bergmann's message of "Fri, 11 Feb 2022 21:57:43 +0100") References: <20220117132757.1881981-1-arnd@kernel.org> <126ae5ee-342c-334c-9c07-c00213dd7b7e@xilinx.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) Date: Fri, 11 Feb 2022 15:10:10 -0600 Message-ID: <87a6exxg7h.fsf@email.froward.int.ebiederm.org> MIME-Version: 1.0 Content-Type: text/plain X-XM-SPF: eid=1nIdBI-001IMe-Qe;;;mid=<87a6exxg7h.fsf@email.froward.int.ebiederm.org>;;;hst=in01.mta.xmission.com;;;ip=68.227.174.4;;;frm=ebiederm@xmission.com;;;spf=neutral X-XM-AID: U2FsdGVkX1+UdMlaxxlAx0910DUy08LRd/8gtAunb88= X-SA-Exim-Connect-IP: 68.227.174.4 X-SA-Exim-Mail-From: ebiederm@xmission.com X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Virus: No X-Spam-DCC: XMission; sa01 1397; Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: ;Arnd Bergmann X-Spam-Relay-Country: X-Spam-Timing: total 1339 ms - load_scoreonly_sql: 0.03 (0.0%), signal_user_changed: 3.3 (0.2%), b_tie_ro: 2.3 (0.2%), parse: 0.68 (0.1%), extract_message_metadata: 8 (0.6%), get_uri_detail_list: 1.15 (0.1%), tests_pri_-1000: 11 (0.8%), tests_pri_-950: 1.06 (0.1%), tests_pri_-900: 0.81 (0.1%), tests_pri_-90: 68 (5.1%), check_bayes: 67 (5.0%), b_tokenize: 6 (0.4%), b_tok_get_all: 6 (0.4%), b_comp_prob: 1.74 (0.1%), b_tok_touch_all: 51 (3.8%), b_finish: 0.68 (0.1%), tests_pri_0: 1233 (92.1%), check_dkim_signature: 0.45 (0.0%), check_dkim_adsp: 1.80 (0.1%), poll_dns_idle: 0.35 (0.0%), tests_pri_10: 2.7 (0.2%), tests_pri_500: 7 (0.5%), rewrite_mail: 0.00 (0.0%) Subject: Re: [PATCH] microblaze: remove CONFIG_SET_FS X-SA-Exim-Version: 4.2.1 (built Sat, 08 Feb 2020 21:53:50 +0000) X-SA-Exim-Scanned: Yes (on in01.mta.xmission.com) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Arnd Bergmann writes: > On Fri, Feb 11, 2022 at 6:46 PM Linus Torvalds > wrote: >> On Fri, Feb 11, 2022 at 9:00 AM Arnd Bergmann wrote: >> > >> > I have now uploaded a cleanup series to >> > https://git.kernel.org/pub/scm/linux/kernel/git/arnd/playground.git/log/?h=set_fs >> > >> > This uses the same access_ok() function across almost all >> > architectures, with the exception of those that need something else, >> > and I then I went further and killed off set_fs for everything other >> > than ia64. >> >> Thanks, looks good to me. >> >> Can you say why you didn't convert ia64? I don't see any set_fs() use >> there, except for the unaligned handler, which looks trivial to >> remove. It looks like the only reason for it is kernel-mode unaligned >> exceptions, which we should just turn fatal, I suspect (they already >> get logged). >> >> And ia64 people could make the unaligned handling do the kernel mode >> case in emulate_load/store_int() - it doesn't look *that* painful. >> >> But maybe you noticed something else? >> >> It would be really good to just be able to say that set_fs() no longer >> exists at all. > > I had previously gotten stuck at ia64, but gave it another go now > and uploaded an updated branch with ia64 taken care of and another > patch to clean up bits afterwards. > > I only gave it light testing so far, mainly building the defconfig for every > architecture. I'll post the series once the build bots are happy with the > branch overall. > Thank you so much for doing this work. Eric