From: Will Deacon <will.deacon@arm.com>
To: Vincenzo Frascino <vincenzo.frascino@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/4] arm64: compat: Add kuser helpers config option
Date: Tue, 16 Apr 2019 22:35:09 +0100 [thread overview]
Message-ID: <20190416213508.GB11724@brain-police> (raw)
In-Reply-To: <20190415094937.13518-1-vincenzo.frascino@arm.com>
On Mon, Apr 15, 2019 at 10:49:33AM +0100, Vincenzo Frascino wrote:
> Currently on arm64 compat kuser helper are enabled by default.
>
> To be on pair with arm32, this patchset makes it possible to disable
> the kuser helpers by adding a CONFIG_KUSER_HELPERS option which is
> enabled by default to avoid compatibility issues.
>
> When the config option is disabled:
> - The kuser helpers-related code is not compiled with the kernel.
> - The kuser helpers mapping, for any compat process, at 0xffff0000
> is not done.
> - Any attempt to use a kuser helper from a compat process will result
> in a segfault.
This looks good for 5.2. I've made a few small cleanups, and I plan to
push out the series next week.
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-04-16 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 9:49 [PATCH v4 0/4] arm64: compat: Add kuser helpers config option Vincenzo Frascino
2019-04-15 9:49 ` [PATCH v4 1/4] arm64: compat: Alloc separate pages for vectors and sigpage Vincenzo Frascino
2019-04-15 9:49 ` [PATCH v4 2/4] arm64: compat: Split kuser32 Vincenzo Frascino
2019-04-15 9:49 ` [PATCH v4 3/4] arm64: compat: Refactor aarch32_alloc_vdso_pages() Vincenzo Frascino
2019-04-15 9:49 ` [PATCH v4 4/4] arm64: compat: Add KUSER_HELPERS config option Vincenzo Frascino
2019-04-16 21:35 ` Will Deacon [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=20190416213508.GB11724@brain-police \
--to=will.deacon@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=vincenzo.frascino@arm.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