public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Kees Cook <keescook@chromium.org>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	KP Singh <kpsingh@kernel.org>, Chris Mason <clm@meta.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	Florent Revest <revest@chromium.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] error-injection: Add prompt for function error injection
Date: Tue, 22 Nov 2022 07:24:04 +0900	[thread overview]
Message-ID: <20221122072404.c55c0c2070c6ebb5230f3813@kernel.org> (raw)
In-Reply-To: <20221121104403.1545f9b5@gandalf.local.home>

On Mon, 21 Nov 2022 10:44:03 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:

> From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
> 
> The config to be able to inject error codes into any function annotated
> with ALLOW_ERROR_INJECTION() is enabled when CONFIG_FUNCTION_ERROR_INJECTION
> is enabled. But unfortunately, this is always enabled on x86 when KPROBES
> is enabled, and there's no way to turn it off.
> 
> As kprobes is useful for observability of the kernel, it is useful to have
> it enabled in production environments. But error injection should be
> avoided. Add a prompt to the config to allow it to be disabled even when
> kprobes is enabled, and get rid of the "def_bool y".
> 
> This is a kernel debug feature (it's in Kconfig.debug), and should have
> never been something enabled by default.
> 

Oops, thanks for update. Yes, it should not be enabled in the production system.

Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>

Thanks,

> Cc: stable@vger.kernel.org
> Fixes: 540adea3809f6 ("error-injection: Separate error-injection from kprobe")
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> ---
>  lib/Kconfig.debug | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
> 
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index c3c0b077ade3..9ee72d8860c3 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -1874,8 +1874,14 @@ config NETDEV_NOTIFIER_ERROR_INJECT
>  	  If unsure, say N.
>  
>  config FUNCTION_ERROR_INJECTION
> -	def_bool y
> +	bool "Fault-injections of functions"
>  	depends on HAVE_FUNCTION_ERROR_INJECTION && KPROBES
> +	help
> +	  Add fault injections into various functions that are annotated with
> +	  ALLOW_ERROR_INJECTION() in the kernel. BPF may also modify the return
> +	  value of theses functions. This is useful to test error paths of code.
> +
> +	  If unsure, say N
>  
>  config FAULT_INJECTION
>  	bool "Fault-injection framework"
> -- 
> 2.35.1
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

      parent reply	other threads:[~2022-11-21 22:24 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-21 15:44 [PATCH] error-injection: Add prompt for function error injection Steven Rostedt
2022-11-21 19:32 ` Borislav Petkov
2022-11-21 23:36   ` Alexei Starovoitov
2022-11-22  0:09     ` Masami Hiramatsu
2022-11-22  0:24     ` Steven Rostedt
2022-11-22  0:40       ` Steven Rostedt
2022-11-22 10:39     ` Borislav Petkov
2022-11-22 17:42       ` Chris Mason
2022-11-22 18:16         ` Borislav Petkov
2022-11-22 18:29         ` Steven Rostedt
2022-11-22 19:51           ` Chris Mason
2022-11-30 22:37             ` Andrew Morton
2022-12-01 16:58               ` Alexei Starovoitov
2022-12-01 17:39                 ` Benjamin Tissoires
2022-12-01 21:12                 ` Andrew Morton
2022-12-01 21:13                 ` Linus Torvalds
2022-12-02  0:46                   ` Jiri Kosina
2022-12-02  0:57                     ` Linus Torvalds
2022-12-02  1:03                       ` Jiri Kosina
2022-12-02  1:32                         ` Steven Rostedt
2022-12-02  1:41                   ` Alexei Starovoitov
2022-12-02 15:56                     ` Theodore Ts'o
2022-12-02 21:27                       ` Alexei Starovoitov
2022-12-02 23:17                         ` Steven Rostedt
2022-12-03  0:55                           ` Alexei Starovoitov
2022-12-04 22:50                         ` Masami Hiramatsu
2022-12-06  2:05                           ` Alexei Starovoitov
2022-12-02 14:55                   ` Benjamin Tissoires
2022-12-02 19:30                     ` Alexei Starovoitov
2022-12-05 17:01                       ` Benjamin Tissoires
2022-12-01 14:41         ` Masami Hiramatsu
2022-12-01 16:37           ` [RFC PATCH] panic: Add new taint flag for fault injection Masami Hiramatsu (Google)
2022-12-01 16:39             ` Kees Cook
2022-12-01 16:48               ` Steven Rostedt
2022-12-01 16:53                 ` Kees Cook
2022-12-01 19:14                   ` Steven Rostedt
2022-12-01 21:00                     ` Chris Mason
2022-12-01 21:18                       ` Linus Torvalds
2022-12-02  6:17                         ` Christoph Hellwig
2022-12-01 21:25                       ` Steven Rostedt
2022-12-01 21:29                         ` Steven Rostedt
2022-12-02  0:46                     ` Masami Hiramatsu
2022-12-01 16:40             ` Steven Rostedt
2022-11-21 22:24 ` Masami Hiramatsu [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=20221122072404.c55c0c2070c6ebb5230f3813@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=clm@meta.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=jpoimboe@redhat.com \
    --cc=keescook@chromium.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=peterz@infradead.org \
    --cc=revest@chromium.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.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