From: Josef Bacik <josef@toxicpanda.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Alexei Starovoitov <ast@fb.com>, Josef Bacik <jbacik@fb.com>,
rostedt@goodmis.org, mingo@redhat.com, davem@davemloft.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
ast@kernel.org, kernel-team@fb.com, daniel@iogearbox.net,
linux-btrfs@vger.kernel.org, darrick.wong@oracle.com,
Josef Bacik <josef@toxicpanda.com>,
Akinobu Mita <akinobu.mita@gmail.com>
Subject: Re: [PATCH bpf-next v3 5/5] error-injection: Support fault injection framework
Date: Wed, 10 Jan 2018 10:42:50 -0500 [thread overview]
Message-ID: <20180110154249.kqkbxzq77wgjwu7p@destiny> (raw)
In-Reply-To: <151557954526.6629.17668573917001919432.stgit@devbox>
On Wed, Jan 10, 2018 at 07:19:05PM +0900, Masami Hiramatsu wrote:
> Support in-kernel fault-injection framework via debugfs.
> This allows you to inject a conditional error to specified
> function using debugfs interfaces.
>
> Here is the result of test script described in
> Documentation/fault-injection/fault-injection.txt
>
> ===========
> # ./test_fail_function.sh
> 1+0 records in
> 1+0 records out
> 1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.0227404 s, 46.1 MB/s
> btrfs-progs v4.4
> See http://btrfs.wiki.kernel.org for more information.
>
> Label: (null)
> UUID: bfa96010-12e9-4360-aed0-42eec7af5798
> Node size: 16384
> Sector size: 4096
> Filesystem size: 1001.00MiB
> Block group profiles:
> Data: single 8.00MiB
> Metadata: DUP 58.00MiB
> System: DUP 12.00MiB
> SSD detected: no
> Incompat features: extref, skinny-metadata
> Number of devices: 1
> Devices:
> ID SIZE PATH
> 1 1001.00MiB /dev/loop2
>
> mount: mount /dev/loop2 on /opt/tmpmnt failed: Cannot allocate memory
> SUCCESS!
> ===========
>
>
> Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
Reviewed-by: Josef Bacik <jbacik@fb.com>
Thanks,
Josef
prev parent reply other threads:[~2018-01-10 15:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 10:16 [PATCH bpf-next v3 0/5] Separate error injection table from kprobes Masami Hiramatsu
2018-01-10 10:17 ` [PATCH bpf-next v3 1/5] tracing/kprobe: bpf: Check error injectable event is on function entry Masami Hiramatsu
2018-01-10 15:21 ` Josef Bacik
2018-01-10 10:17 ` [PATCH bpf-next v3 2/5] tracing/kprobe: bpf: Compare instruction pointer with original one Masami Hiramatsu
2018-01-10 15:24 ` Josef Bacik
2018-01-10 10:18 ` [PATCH bpf-next v3 3/5] error-injection: Separate error-injection from kprobe Masami Hiramatsu
2018-01-10 15:36 ` Josef Bacik
2018-01-10 22:18 ` Masami Hiramatsu
2018-01-10 10:18 ` [PATCH bpf-next v3 4/5] error-injection: Add injectable error types Masami Hiramatsu
2018-01-10 15:38 ` Josef Bacik
2018-01-10 10:19 ` [PATCH bpf-next v3 5/5] error-injection: Support fault injection framework Masami Hiramatsu
2018-01-10 15:42 ` Josef Bacik [this message]
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=20180110154249.kqkbxzq77wgjwu7p@destiny \
--to=josef@toxicpanda.com \
--cc=akinobu.mita@gmail.com \
--cc=ast@fb.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=darrick.wong@oracle.com \
--cc=davem@davemloft.net \
--cc=jbacik@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.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