All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Gregory Price <gourry.memverge@gmail.com>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-arch@vger.kernel.org, avagin@gmail.com,
	peterz@infradead.org, luto@kernel.org, krisman@collabora.com,
	tglx@linutronix.de, corbet@lwn.net, shuah@kernel.org,
	arnd@arndb.de, Gregory Price <gregory.price@memverge.com>
Subject: Re: [PATCH v15 2/4] syscall user dispatch: untag selector addresses before access_ok
Date: Wed, 5 Apr 2023 18:02:28 +0200	[thread overview]
Message-ID: <20230405160227.GA13943@redhat.com> (raw)
In-Reply-To: <ZC1UEK43yOsXKvi4@arm.com>

On 04/05, Catalin Marinas wrote:
>
> > Yes, from the security perspective, but there are ABI implications.

Thanks a lot for your explanations.

To be honest, I am still a bit confused... Will try to grep the relevant code.
But as for this patch, now I believe it is correct.

So, FWIW,

Acked-by: Oleg Nesterov <oleg@redhat.com>


  reply	other threads:[~2023-04-05 16:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 21:21 [PATCH v15 0/4] Checkpoint Support for Syscall User Dispatch Gregory Price
2023-03-30 21:21 ` [PATCH v15 1/4] syscall_user_dispatch: helper function to operate on given task Gregory Price
2023-03-30 21:21 ` [PATCH v15 2/4] syscall user dispatch: untag selector addresses before access_ok Gregory Price
2023-03-30 22:40   ` Catalin Marinas
2023-04-04 10:45     ` Oleg Nesterov
2023-04-04 17:33       ` Catalin Marinas
2023-04-05 10:57         ` Catalin Marinas
2023-04-05 16:02           ` Oleg Nesterov [this message]
2023-03-30 21:21 ` [PATCH v15 3/4] ptrace,syscall_user_dispatch: checkpoint/restore support for SUD Gregory Price
2023-03-30 21:21 ` [PATCH v15 4/4] selftest,ptrace: Add selftest for syscall user dispatch config api Gregory Price

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=20230405160227.GA13943@redhat.com \
    --to=oleg@redhat.com \
    --cc=arnd@arndb.de \
    --cc=avagin@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=gourry.memverge@gmail.com \
    --cc=gregory.price@memverge.com \
    --cc=krisman@collabora.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=peterz@infradead.org \
    --cc=shuah@kernel.org \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.