[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <24095989-57be-332c-f08c-acb1672c7e6f@c-s.fr>
Date: Thu, 2 Apr 2020 20:35:09 +0200
From: Christophe Leroy <christophe.leroy@....fr>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
Michael Ellerman <mpe@...erman.id.au>, airlied@...ux.ie,
daniel@...ll.ch, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, keescook@...omium.org, hpa@...or.com,
linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
linux-mm@...ck.org, linux-arch@...r.kernel.org,
Russell King <linux@...linux.org.uk>,
Christian Borntraeger <borntraeger@...ibm.com>
Subject: Re: [PATCH RESEND 1/4] uaccess: Add user_read_access_begin/end and
user_write_access_begin/end
Le 02/04/2020 à 19:50, Al Viro a écrit :
> On Thu, Apr 02, 2020 at 07:03:28PM +0200, Christophe Leroy wrote:
>
>> user_access_begin() grants both read and write.
>>
>> This patch adds user_read_access_begin() and user_write_access_begin() but
>> it doesn't remove user_access_begin()
>
> Ouch... So the most generic name is for the rarest case?
>
I can add another patch at the end of the series to rename
user_access_begin() to user_full_access_begin().
Would it suit you ?
Christophe
Powered by blists - more mailing lists