linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Darren Hart <dvhart@infradead.org>,
	Davidlohr Bueso <dave@stgolabs.net>,
	Andre Almeida <andrealmeid@igalia.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Eric Dumazet <edumazet@google.com>,
	Kuniyuki Iwashima <kuniyu@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Willem de Bruijn <willemb@google.com>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Nicholas Piggin <npiggin@gmail.com>
Cc: linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 03/10] uaccess: Add masked_user_{read/write}_access_begin
Date: Tue, 04 Nov 2025 09:01:58 +0100	[thread overview]
Message-ID: <875xbqw7ih.ffs@tglx> (raw)
In-Reply-To: <01d89f24-8fca-4fc3-9f48-79e28b9663db@csgroup.eu>

On Tue, Nov 04 2025 at 07:39, Christophe Leroy wrote:
> Le 22/10/2025 à 19:05, Thomas Gleixner a écrit :
>> On Fri, Oct 17 2025 at 12:20, Christophe Leroy wrote:
>>> Allthough masked_user_access_begin() is to only be used when reading
>>> data from user at the moment, introduce masked_user_read_access_begin()
>>> and masked_user_write_access_begin() in order to match
>>> user_read_access_begin() and user_write_access_begin().
>>>
>>> That means masked_user_read_access_begin() is used when user memory is
>>> exclusively read during the window, masked_user_write_access_begin()
>>> is used when user memory is exclusively writen during the window,
>>> masked_user_access_begin() remains and is used when both reads and
>>> writes are performed during the open window. Each of them is expected
>>> to be terminated by the matching user_read_access_end(),
>>> user_write_access_end() and user_access_end().
>>>
>>> Have them default to masked_user_access_begin() when they are
>>> not defined.
>>>
>>> Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
>> 
>> Can we please coordinate on that vs. the scoped_access() work as this
>> nicely collides all over the place?
>
> Sure, I will rebase on top of your series.
>
> Once it is rebased, could you take the non powerpc patches in your tree ?

Sure. The current lot is at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git scoped-uaccess

Thanks,

        tglx

  reply	other threads:[~2025-11-04  8:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17 10:20 [PATCH v3 00/10] powerpc: Implement masked user access Christophe Leroy
2025-10-17 10:20 ` [PATCH v3 01/10] iter: Avoid barrier_nospec() in copy_from_user_iter() Christophe Leroy
2025-10-17 10:20 ` [PATCH v3 02/10] uaccess: Add speculation barrier to copy_from_user_iter() Christophe Leroy
2025-10-17 10:20 ` [PATCH v3 03/10] uaccess: Add masked_user_{read/write}_access_begin Christophe Leroy
2025-10-22 17:05   ` Thomas Gleixner
2025-11-04  6:39     ` Christophe Leroy
2025-11-04  8:01       ` Thomas Gleixner [this message]
2025-10-17 10:21 ` [PATCH v3 04/10] powerpc/uaccess: Move barrier_nospec() out of allow_read_{from/write}_user() Christophe Leroy
2025-10-17 10:21 ` [PATCH v3 05/10] powerpc/uaccess: Remove unused size and from parameters from allow_access_user() Christophe Leroy
2025-10-17 10:21 ` [PATCH v3 06/10] powerpc/uaccess: Remove {allow/prevent}_{read/write/read_write}_{from/to/}_user() Christophe Leroy
2025-10-17 10:21 ` [PATCH v3 07/10] powerpc/uaccess: Refactor user_{read/write/}_access_begin() Christophe Leroy
2025-10-17 10:21 ` [PATCH v3 08/10] powerpc/32s: Fix segments setup when TASK_SIZE is not a multiple of 256M Christophe Leroy
2025-10-17 10:21 ` [PATCH v3 09/10] powerpc/32: Automatically adapt TASK_SIZE based on constraints Christophe Leroy
2025-10-17 10:21 ` [PATCH v3 10/10] powerpc/uaccess: Implement masked user access Christophe Leroy
2025-10-21  6:34   ` Gabriel Paubert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875xbqw7ih.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=andrealmeid@igalia.com \
    --cc=brauner@kernel.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=daniel@iogearbox.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=dave@stgolabs.net \
    --cc=davem@davemloft.net \
    --cc=dvhart@infradead.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jack@suse.cz \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mingo@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=netdev@vger.kernel.org \
    --cc=npiggin@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=peterz@infradead.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willemb@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).