From: Andrew Morton <akpm@linux-foundation.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: akinobu.mita@gmail.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2] fault-inject: support systematic fault injection
Date: Tue, 28 Mar 2017 14:40:03 -0700 [thread overview]
Message-ID: <20170328144003.b7f7b699f3d22616064e8f7e@linux-foundation.org> (raw)
In-Reply-To: <20170328130128.101773-1-dvyukov@google.com>
On Tue, 28 Mar 2017 15:01:28 +0200 Dmitry Vyukov <dvyukov@google.com> wrote:
> Add /proc/self/task/<current-tid>/fail-nth file that allows failing
> 0-th, 1-st, 2-nd and so on calls systematically.
> Excerpt from the added documentation:
>
> ===
> Write to this file of integer N makes N-th call in the current task fail
> (N is 0-based). Read from this file returns a single char 'Y' or 'N'
> that says if the fault setup with a previous write to this file was
> injected or not, and disables the fault if it wasn't yet injected.
> Note that this file enables all types of faults (slab, futex, etc).
> This setting takes precedence over all other generic settings like
> probability, interval, times, etc. But per-capability settings
> (e.g. fail_futex/ignore-private) take precedence over it.
> This feature is intended for systematic testing of faults in a single
> system call. See an example below.
> ===
>
> Why adding new setting:
> 1. Existing settings are global rather than per-task.
> So parallel testing is not possible.
> 2. attr->interval is close but it depends on attr->count
> which is non reset to 0, so interval does not work as expected.
> 3. Trying to model this with existing settings requires manipulations
> of all of probability, interval, times, space, task-filter and
> unexposed count and per-task make-it-fail files.
> 4. Existing settings are per-failure-type, and the set of failure
> types is potentially expanding.
> 5. make-it-fail can't be changed by unprivileged user and aggressive
> stress testing better be done from an unprivileged user.
> Similarly, this would require opening the debugfs files to the
> unprivileged user, as he would need to reopen at least times file
> (not possible to pre-open before dropping privs).
>
> The proposed interface solves all of the above (see the example).
Seems reasonable.
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -1897,6 +1897,7 @@ struct task_struct {
> #endif
> #ifdef CONFIG_FAULT_INJECTION
> int make_it_fail;
> + int fail_nth;
> #endif
Nit: fail_nth should really be unsigned. And make_it_fail could be
made a single bit which shares storage with brk_randomized (for
example).
next prev parent reply other threads:[~2017-03-28 21:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 13:01 Dmitry Vyukov
2017-03-28 21:40 ` Andrew Morton [this message]
2017-03-28 23:41 ` Akinobu Mita
2017-03-30 23:04 ` Andrew Morton
2017-04-04 14:57 ` Akinobu Mita
2017-04-06 18:33 ` Michal Hocko
2017-04-07 16:47 ` Akinobu Mita
2017-04-08 17:40 ` Dmitry Vyukov
2017-04-09 10:39 ` Akinobu Mita
2017-05-24 10:22 ` Dmitry Vyukov
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=20170328144003.b7f7b699f3d22616064e8f7e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=akinobu.mita@gmail.com \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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®