Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp2609348ybb; Sun, 5 Apr 2020 11:50:07 -0700 (PDT) X-Google-Smtp-Source: APiQypKrYePGz7ny3rd/1pAI/D4S4ns3ZIphodTjBAELHbOwtvFOwAPHMvlu1GueHK63d/UI3DRS X-Received: by 2002:a05:6830:3090:: with SMTP id f16mr14276262ots.211.1586112607711; Sun, 05 Apr 2020 11:50:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586112607; cv=none; d=google.com; s=arc-20160816; b=um7DgJnWVimdXULtTJ0cuZzOfdQtL4p7K4uwVxw4StzKsIX4Mwt6dXGteaWvjVGPqP GOXlPvnbSfwXTQjg5AiGKwQ3oNkcu/gBIQxiNaO06uCEOPej8LbqcDepp2cuwml0bTL2 LJF84v10PWHzFtIeP8kzBShLk+VJ394bhcF0URkR26ZVnwXEY0g1MpmQaqk9rl0hGING M69IGZ1ByZfDDuxH4KU4wCEbykU1o382FWwYHaOPBuNojHcv3p9/JYSesdMBpQ7tzbI2 H2OmfM6kvDMYxPor50inDjeEH4jklKq/WXDmGAV3tfbIPE8KDVQuABbPJFZ/vOANRqsp qatQ== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=5K5fWcVt/dZhMcfYZl39DOWw/ijhu2ZfXrNWbrQtW5w=; b=x8RPQ7lBgNu16ryL/7jRVxtf4u9x8s1QTx2YGTZYohbVML3uCuoq4353BuqPIcKjPr MO0MlpQkZE4HX486nwWcN2r0ZVG14B9tlykmI+tWwIernRpIifcSWk1v4gKjEG27Hs3M hpCn5082ARvvfnH+4eA5G747LSiW9fsFWSG6b/n3KsVtfizFkngCfMJS23eBgg3pw+Zy 4BgwSN4MxpdKUmF97qpSNNKXYp70n1p9as3EcxZQLyldf7KUGRcbI5gc37aXX5nPomiq PCtMDNdp7UCls7F6cpOKNqTpGg34Evkjtw9CTrpjHeb693Fxtowrre7KlY51FbSrbJRA T2uQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@c-s.fr header.s=mail header.b=vDT4kbDd; 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 m25si7148547otq.210.2020.04.05.11.49.55; Sun, 05 Apr 2020 11:50:07 -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; dkim=pass header.i=@c-s.fr header.s=mail header.b=vDT4kbDd; 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 S1727522AbgDESsE (ORCPT + 99 others); Sun, 5 Apr 2020 14:48:04 -0400 Received: from pegase1.c-s.fr ([93.17.236.30]:17029 "EHLO pegase1.c-s.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726771AbgDESsE (ORCPT ); Sun, 5 Apr 2020 14:48:04 -0400 Received: from localhost (mailhub1-int [192.168.12.234]) by localhost (Postfix) with ESMTP id 48wN326Bkfz9tx5R; Sun, 5 Apr 2020 20:47:58 +0200 (CEST) Authentication-Results: localhost; dkim=pass reason="1024-bit key; insecure key" header.d=c-s.fr header.i=@c-s.fr header.b=vDT4kbDd; dkim-adsp=pass; dkim-atps=neutral X-Virus-Scanned: Debian amavisd-new at c-s.fr Received: from pegase1.c-s.fr ([192.168.12.234]) by localhost (pegase1.c-s.fr [192.168.12.234]) (amavisd-new, port 10024) with ESMTP id QLy_PZYARygD; Sun, 5 Apr 2020 20:47:58 +0200 (CEST) Received: from messagerie.si.c-s.fr (messagerie.si.c-s.fr [192.168.25.192]) by pegase1.c-s.fr (Postfix) with ESMTP id 48wN3250PRz9tx5Q; Sun, 5 Apr 2020 20:47:58 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=c-s.fr; s=mail; t=1586112478; bh=5K5fWcVt/dZhMcfYZl39DOWw/ijhu2ZfXrNWbrQtW5w=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=vDT4kbDd2d2luI9YlINWxSulY5GzJlc/jwO7NCfKm9AMRlr2bdQic4qJizaWFEb5/ qcVnWwGTahszH0Ix4iGZVUn3QMwmYXlQ3jAlShEJm0JRShtjY55DPEHrt9faonT8l/ CcmWKseqFccIl50tAZWfd0By1014uveiS11CdABY= Received: from localhost (localhost [127.0.0.1]) by messagerie.si.c-s.fr (Postfix) with ESMTP id 312BE8B783; Sun, 5 Apr 2020 20:48:02 +0200 (CEST) X-Virus-Scanned: amavisd-new at c-s.fr Received: from messagerie.si.c-s.fr ([127.0.0.1]) by localhost (messagerie.si.c-s.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id Y8LGSBfSdJTp; Sun, 5 Apr 2020 20:48:02 +0200 (CEST) Received: from [192.168.4.90] (unknown [192.168.4.90]) by messagerie.si.c-s.fr (Postfix) with ESMTP id A4AC08B774; Sun, 5 Apr 2020 20:48:00 +0200 (CEST) Subject: Re: [PATCH v2 5/5] uaccess: Rename user_access_begin/end() to user_full_access_begin/end() To: Linus Torvalds , Michael Ellerman Cc: Benjamin Herrenschmidt , Paul Mackerras , Dave Airlie , Daniel Vetter , Al Viro , Andrew Morton , Kees Cook , Peter Anvin , Linux Kernel Mailing List , linuxppc-dev , Linux-MM , linux-arch , intel-gfx@lists.freedesktop.org References: <36e43241c7f043a24b5069e78c6a7edd11043be5.1585898438.git.christophe.leroy@c-s.fr> <42da416106d5c1cf92bda1e058434fe240b35f44.1585898438.git.christophe.leroy@c-s.fr> From: Christophe Leroy Message-ID: <0e5985d7-e73b-455b-6b05-351831f09340@c-s.fr> Date: Sun, 5 Apr 2020 20:47:26 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Le 03/04/2020 à 20:01, Linus Torvalds a écrit : > On Fri, Apr 3, 2020 at 12:21 AM Christophe Leroy > wrote: >> >> Now we have user_read_access_begin() and user_write_access_begin() >> in addition to user_access_begin(). > > I realize Al asked for this, but I don't think it really adds anything > to the series. > > The "full" makes the names longer, but not really any more legible. > > So I like 1-4, but am unconvinced about 5 and would prefer that to be > dropped. Sorry for the bikeshedding. > Yes I was not sure about it, that's the reason why I added it as the last patch of the series. And in the meantime, we see Robots reporting build failures due to additional use of user_access_begin() in parallele to this change, so I guess it would anyway be a challenge to perform such a change without coordination. > And I like this series much better without the cookie that was > discussed, and just making the hard rule be that they can't nest. > > Some architecture may obviously use a cookie internally if they have > some nesting behavior of their own, but it doesn't look like we have > any major reason to expose that as the actual interface. > > The only other question is how to synchronize this? I'm ok with it > going through the ppc tree, for example, and just let others build on > that. Maybe using a shared immutable branch with 5.6 as a base? Michael, can you take patches 1 to 4 ? Otherwise, can you ack patch 4 to enable merging through another tree ? Christophe