From: Andrew Morton <akpm@linux-foundation.org>
To: albert.linde@gmail.com
Cc: bp@alien8.de, mingo@redhat.com, corbet@lwn.net,
tglx@linutronix.de, arnd@arndb.de, peterz@infradead.org,
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 van der Linde <alinde@google.com>
Subject: Re: [PATCH v3 0/3] add fault injection to user memory access
Date: Mon, 31 Aug 2020 11:32:38 -0700 [thread overview]
Message-ID: <20200831113238.b6b38076bb02076458592a3d@linux-foundation.org> (raw)
In-Reply-To: <20200831171733.955393-1-alinde@google.com>
On Mon, 31 Aug 2020 17:17:30 +0000 albert.linde@gmail.com wrote:
> 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.
Does anyone actually plan to use this feature, on an ongoing basis?
It's the sort of thing which the various test robots could exploit, but
I'm not sure that they are using fault injection?
next prev parent reply other threads:[~2020-08-31 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 17:17 albert.linde
2020-08-31 17:17 ` [PATCH v3 1/3] lib, include/linux: add usercopy failure capability albert.linde
2020-08-31 17:17 ` [PATCH v3 2/3] lib, uaccess: add failure injection to usercopy functions albert.linde
2020-08-31 17:17 ` [PATCH v3 3/3] x86: add failure injection to get/put/clear_user albert.linde
2020-08-31 18:32 ` Andrew Morton [this message]
2020-08-31 18:59 ` [PATCH v3 0/3] add fault injection to user memory access Andrey Konovalov
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=20200831113238.b6b38076bb02076458592a3d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=akinobu.mita@gmail.com \
--cc=albert.linde@gmail.com \
--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=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®