[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221121104548.4a7aa3de@gandalf.local.home>
Date: Mon, 21 Nov 2022 10:45:48 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: KP Singh <kpsingh@...nel.org>, Chris Mason <clm@...a.com>,
Mark Rutland <mark.rutland@....com>,
Florent Revest <revest@...omium.org>,
bpf <bpf@...r.kernel.org>, Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>,
Brendan Jackman <jackmanb@...gle.com>, markowsky@...gle.com,
Masami Hiramatsu <mhiramat@...nel.org>,
Xu Kuohai <xukuohai@...wei.com>,
LKML <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Christoph Hellwig <hch@...radead.org>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [RFC 0/1] BPF tracing for arm64 using fprobe
On Mon, 21 Nov 2022 07:40:11 -0800
Alexei Starovoitov <alexei.starovoitov@...il.com> wrote:
> >
> > As kprobes are set in most production environments, so is error injection.
> > Do we really want error injection enabled on production environments?
>
> We absolutely want it enabled in production.
>
> > I don't.
>
> Speak for yourself, because your employer thinks otherwise.
And speak for yourself! Just because you want it in production, does not
mean that everyone else is forced to do so too.
It's a DEBUG feature. It's in Kconfig.debug. Why is it enabled by default???
-- Steve
Powered by blists - more mailing lists