From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Christophe LEROY <christophe.leroy@c-s.fr>,
Russell Currey <ruscur@russell.cc>
Cc: mikey@neuling.org, linuxppc-dev@lists.ozlabs.org, npiggin@gmail.com
Subject: Re: [PATCH 0/5] Guarded Userspace Access Prevention on Radix
Date: Fri, 09 Nov 2018 07:09:09 +1100 [thread overview]
Message-ID: <158f2b8a16915bc13d209c1acd38ef5e4e363d3d.camel@kernel.crashing.org> (raw)
In-Reply-To: <3b8d2b1b-548b-5a07-4358-4e645c06f59e@c-s.fr>
On Thu, 2018-11-08 at 18:52 +0100, Christophe LEROY wrote:
>
> In signal_32.c and signal_64.c, save_user_regs() calls __put_user() to
> modify code, then calls flush_icache_range() on user addresses.
>
> Shouldn't flush_icache_range() be performed with userspace access
> protection unlocked ?
Thankfully this code is pretty much never used these days...
Russell: To trigger that, you need to disable the VDSO.
This brings back the idea however of having a way to "bulk" open the
gate during the whole signal sequence...
Cheers,
Ben.
prev parent reply other threads:[~2018-11-08 20:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 6:35 [PATCH 0/5] Guarded Userspace Access Prevention on Radix Russell Currey
2018-10-26 6:35 ` [PATCH 1/5] powerpc/64s: Guarded Userspace Access Prevention Russell Currey
2018-10-26 8:20 ` kbuild test robot
2018-10-28 17:57 ` LEROY Christophe
2018-10-31 4:00 ` Russell Currey
2018-10-31 16:54 ` LEROY Christophe
2018-10-29 13:27 ` kbuild test robot
2018-10-26 6:35 ` [PATCH 2/5] powerpc/futex: GUAP support for futex ops Russell Currey
2018-10-26 16:32 ` LEROY Christophe
2018-10-29 1:08 ` Russell Currey
2018-10-26 6:35 ` [PATCH 3/5] powerpc/lib: checksum GUAP support Russell Currey
2018-10-26 16:33 ` LEROY Christophe
2018-10-26 6:35 ` [PATCH 4/5] powerpc/64s: Disable GUAP with nosmap option Russell Currey
2018-10-26 6:35 ` [PATCH 5/5] powerpc/64s: Document that PPC supports nosmap Russell Currey
2018-10-26 16:35 ` LEROY Christophe
2018-10-29 1:06 ` Russell Currey
2018-10-31 17:06 ` LEROY Christophe
2018-10-26 16:29 ` [PATCH 0/5] Guarded Userspace Access Prevention on Radix LEROY Christophe
2018-10-31 3:53 ` Russell Currey
2018-10-31 16:58 ` LEROY Christophe
2018-11-01 3:54 ` Russell Currey
2018-11-08 17:52 ` Christophe LEROY
2018-11-08 20:09 ` Benjamin Herrenschmidt [this message]
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=158f2b8a16915bc13d209c1acd38ef5e4e363d3d.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=npiggin@gmail.com \
--cc=ruscur@russell.cc \
/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).