From: Julien Thierry <julien.thierry@arm.com>
To: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: mingo@redhat.com, peterz@infradead.org, catalin.marinas@arm.com,
will.deacon@arm.com, james.morse@arm.com, hpa@zytor.com,
Julien Thierry <julien.thierry@arm.com>
Subject: [PATCH v2 0/2] uaccess: Add unsafe accessors for arm64
Date: Mon, 3 Dec 2018 13:55:16 +0000 [thread overview]
Message-ID: <1543845318-24543-1-git-send-email-julien.thierry@arm.com> (raw)
Hi,
First version of this series[1] was briefly in linux-next but had to be
reverted due to a bug where schedule would end up being called while
user_access was active[2].
After clarifications[3], rescheduling while in a user_access region is not
allowed.
* Patch 1 clarifies this restriction in the API and attempts to check
against violations of the restriction.
* Patch 2 implements the unsafe accessors for arm64
Changes since v1:
- Add a way to detect code calling schedule within a user_access region
- Make sure put_user/get_user arguments are evaluated before disabling PAN
[1] https://www.spinics.net/lists/arm-kernel/msg674925.html
[2] https://patchwork.kernel.org/patch/10634783/
[3] https://lkml.org/lkml/2018/11/28/50
Cheers,
Julien
-->
Julien Thierry (2):
uaccess: Check no rescheduling function is called in unsafe region
arm64: uaccess: Implement unsafe accessors
arch/arm64/include/asm/sysreg.h | 2 +
arch/arm64/include/asm/uaccess.h | 89 +++++++++++++++++++++++++++++++---------
include/linux/kernel.h | 6 ++-
include/linux/uaccess.h | 11 +++++
kernel/sched/core.c | 19 +++++++++
5 files changed, 105 insertions(+), 22 deletions(-)
--
1.9.1
next reply other threads:[~2018-12-03 13:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 13:55 Julien Thierry [this message]
2018-12-03 13:55 ` [RFC PATCH v2 1/2] uaccess: Check no rescheduling function is called in unsafe region Julien Thierry
2019-01-14 12:03 ` Valentin Schneider
2019-01-15 11:48 ` Julien Thierry
2018-12-03 13:55 ` [PATCH v2 2/2] arm64: uaccess: Implement unsafe accessors Julien Thierry
2018-12-06 18:25 ` Catalin Marinas
2018-12-07 8:38 ` Julien Thierry
2018-12-10 14:59 ` Catalin Marinas
2018-12-12 17:40 ` Suzuki K Poulose
2018-12-21 14:57 ` James Morse
2018-12-21 14:57 ` James Morse
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=1543845318-24543-1-git-send-email-julien.thierry@arm.com \
--to=julien.thierry@arm.com \
--cc=catalin.marinas@arm.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will.deacon@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;
as well as URLs for NNTP newsgroup(s).