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 v4 3/5] error-injection: Separate error-injection from kprobe
Date: Thu, 11 Jan 2018 11:40:16 -0500 [thread overview]
Message-ID: <20180111164013.smpmaftyxpufe4ak@destiny> (raw)
In-Reply-To: <151563182380.628.2420967932180154822.stgit@devbox>
On Thu, Jan 11, 2018 at 09:50:24AM +0900, Masami Hiramatsu wrote:
> Since error-injection framework is not limited to be used
> by kprobes, nor bpf. Other kernel subsystems can use it
> freely for checking safeness of error-injection, e.g.
> livepatch, ftrace etc.
> So this separate error-injection framework from kprobes.
>
> Some differences has been made:
>
> - "kprobe" word is removed from any APIs/structures.
> - BPF_ALLOW_ERROR_INJECTION() is renamed to
> ALLOW_ERROR_INJECTION() since it is not limited for BPF too.
> - CONFIG_FUNCTION_ERROR_INJECTION is the config item of this
> feature. It is automatically enabled if the arch supports
> error injection feature for kprobe or ftrace etc.
>
> Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
Reviewed-by: Josef Bacik <jbacik@fb.com>
Thanks,
Josef
next prev parent reply other threads:[~2018-01-11 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 0:48 [PATCH bpf-next v4 0/5] Separate error injection table from kprobes Masami Hiramatsu
2018-01-11 0:49 ` [PATCH bpf-next v4 1/5] tracing/kprobe: bpf: Check error injectable event is on function entry Masami Hiramatsu
2018-01-11 0:49 ` [PATCH bpf-next v4 2/5] tracing/kprobe: bpf: Compare instruction pointer with original one Masami Hiramatsu
2018-01-11 0:50 ` [PATCH bpf-next v4 3/5] error-injection: Separate error-injection from kprobe Masami Hiramatsu
2018-01-11 16:40 ` Josef Bacik [this message]
2018-01-11 0:50 ` [PATCH bpf-next v4 4/5] error-injection: Add injectable error types Masami Hiramatsu
2018-01-11 0:51 ` [PATCH bpf-next v4 5/5] error-injection: Support fault injection framework Masami Hiramatsu
2018-01-11 14:44 ` Akinobu Mita
2018-01-11 16:15 ` Masami Hiramatsu
2018-01-12 0:30 ` Akinobu Mita
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=20180111164013.smpmaftyxpufe4ak@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.