[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <b0d8da28-2499-48db-be17-7d126697e303@app.fastmail.com>
Date: Tue, 28 Mar 2023 20:46:06 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Gregory Price" <gourry.memverge@...il.com>,
linux-kernel@...r.kernel.org
Cc: linux-doc@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Linux-Arch <linux-arch@...r.kernel.org>,
"Oleg Nesterov" <oleg@...hat.com>, avagin@...il.com,
"Peter Zijlstra" <peterz@...radead.org>,
"Andy Lutomirski" <luto@...nel.org>, krisman@...labora.com,
"Thomas Gleixner" <tglx@...utronix.de>,
"Jonathan Corbet" <corbet@....net>, shuah <shuah@...nel.org>,
"Catalin Marinas" <catalin.marinas@....com>,
"Will Deacon" <will@...nel.org>,
"Mark Rutland" <mark.rutland@....com>, tongtiangen@...wei.com,
"Robin Murphy" <robin.murphy@....com>,
"Gregory Price" <gregory.price@...verge.com>
Subject: Re: [PATCH v14 1/4] asm-generic,arm64: create task variant of access_ok
On Tue, Mar 28, 2023, at 18:48, Gregory Price wrote:
> On arm64, access_ok makes adjustments to pointers based on whether
> memory tagging is enabled for a task (ARM MTE). When leveraging ptrace,
> it's possible for a task to enable/disable various kernel features (such
> as syscall user dispatch) which require user points as arguments.
>
> To enable Task A to set these features via ptrace with Task B's
> pointers, a task variant of access_ok is required for architectures with
> features such as memory tagging.
>
> If the architecture does not implement task_access_ok, the operation
> reduces to access_ok and the task argument is discarded.
>
> Signed-off-by: Gregory Price <gregory.price@...verge.com>
For asm-generic:
Acked-by: Arnd Bergmann <arnd@...db.de>
Powered by blists - more mailing lists