From: albert.linde@gmail.com
To: akpm@linux-foundation.org, bp@alien8.de, mingo@redhat.com,
corbet@lwn.net, tglx@linutronix.de, arnd@arndb.de
Cc: akinobu.mita@gmail.com, hpa@zytor.com, viro@zeniv.linux.org.uk,
glider@google.com, andreyknvl@google.com, dvyukov@google.com,
elver@google.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
x86@kernel.org, albert.linde@gmail.com,
Albert van der Linde <alinde@google.com>
Subject: [PATCH v2 0/3] add fault injection to user memory access
Date: Fri, 28 Aug 2020 14:13:41 +0000 [thread overview]
Message-ID: <20200828141344.2277088-1-alinde@google.com> (raw)
From: Albert van der Linde <alinde@google.com>
The goal of this series is to improve testing of fault-tolerance in
usages of user memory access functions, by adding support for fault
injection.
The first patch adds failure injection capability for usercopy
functions. The second changes usercopy functions to use this new failure
capability (copy_from_user, ...). The third patch adds
get/put/clear_user failures to x86.
Changes in v2:
- simplified overall failure capability by either failing or not, without
having functions fail partially by copying/clearing only some bytes
Albert van der Linde (3):
lib, include/linux: add usercopy failure capability
lib, uaccess: add failure injection to usercopy functions
x86: add failure injection to get/put/clear_user
.../admin-guide/kernel-parameters.txt | 1 +
.../fault-injection/fault-injection.rst | 7 +-
arch/x86/include/asm/uaccess.h | 68 +++++++++++--------
arch/x86/lib/usercopy_64.c | 3 +
include/linux/fault-inject-usercopy.h | 22 ++++++
include/linux/uaccess.h | 11 ++-
lib/Kconfig.debug | 7 ++
lib/Makefile | 1 +
lib/fault-inject-usercopy.c | 39 +++++++++++
lib/iov_iter.c | 5 ++
lib/strncpy_from_user.c | 3 +
lib/usercopy.c | 5 +-
12 files changed, 140 insertions(+), 32 deletions(-)
create mode 100644 include/linux/fault-inject-usercopy.h
create mode 100644 lib/fault-inject-usercopy.c
--
2.28.0.402.g5ffc5be6b7-goog
next reply other threads:[~2020-08-28 14:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 14:13 albert.linde [this message]
2020-08-28 14:13 ` [PATCH v2 1/3] lib, include/linux: add usercopy failure capability albert.linde
2020-08-28 14:13 ` [PATCH v2 2/3] lib, uaccess: add failure injection to usercopy functions albert.linde
2020-08-31 16:21 ` peterz
2020-08-28 14:13 ` [PATCH v2 3/3] x86: add failure injection to get/put/clear_user albert.linde
2020-08-31 14:29 ` [PATCH v2 0/3] add fault injection to user memory access Akinobu Mita
2020-08-31 15:49 ` Alexander Potapenko
2020-08-31 16:27 ` Akinobu Mita
2020-08-31 18:31 ` Alexander Potapenko
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=20200828141344.2277088-1-alinde@google.com \
--to=albert.linde@gmail.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alinde@google.com \
--cc=andreyknvl@google.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.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).