From: Paul Mackerras <paulus@ozlabs.org>
To: linuxppc-dev@ozlabs.org
Subject: [PATCH v3 0/4] powerpc/64: copy_tofrom_user exception handling improvements
Date: Fri, 3 Aug 2018 20:13:02 +1000 [thread overview]
Message-ID: <1533291186-5374-1-git-send-email-paulus@ozlabs.org> (raw)
This is a repost of a series that I posted back in 2016 but which was
never applied. It aims to make the exception handling code in
__copy_tofrom_user_base clearer and easier to verify, and strengthens
the selftests for the user copy code to test all the paths and to test
the exception handling. Finally it then fixes a deficiency in that
when copying to userspace we don't always copy quite as many bytes as
we could.
I have rebased this series on top of the powerpc next branch as of
today.
Paul.
arch/powerpc/lib/copyuser_64.S | 585 +++++++++------------
arch/powerpc/lib/copyuser_power7.S | 21 +-
arch/powerpc/lib/memcpy_64.S | 9 +-
arch/powerpc/lib/memcpy_power7.S | 22 +-
.../testing/selftests/powerpc/copyloops/.gitignore | 17 +-
tools/testing/selftests/powerpc/copyloops/Makefile | 44 +-
.../selftests/powerpc/copyloops/asm/ppc_asm.h | 44 +-
.../powerpc/copyloops/copy_tofrom_user_reference.S | 24 +
.../selftests/powerpc/copyloops/exc_validate.c | 124 +++++
tools/testing/selftests/powerpc/copyloops/stubs.S | 19 +
10 files changed, 516 insertions(+), 393 deletions(-)
next reply other threads:[~2018-08-03 10:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 10:13 Paul Mackerras [this message]
2018-08-03 10:13 ` [PATCH v3 1/4] powerpc/64: Make exception table clearer in __copy_tofrom_user_base Paul Mackerras
2018-08-08 14:26 ` [v3, " Michael Ellerman
2018-08-03 10:13 ` [PATCH v3 2/4] selftests/powerpc/64: Test all paths through copy routines Paul Mackerras
2018-08-03 10:13 ` [PATCH v3 3/4] selftests/powerpc/64: Test exception cases in copy_tofrom_user Paul Mackerras
2018-08-03 10:13 ` [PATCH v3 4/4] powerpc/64: Copy as much as possible in __copy_tofrom_user Paul Mackerras
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=1533291186-5374-1-git-send-email-paulus@ozlabs.org \
--to=paulus@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
/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).