[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221130143719.07e36277d1471b83e9a1b627@linux-foundation.org>
Date: Wed, 30 Nov 2022 14:37:19 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Chris Mason <clm@...a.com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Borislav Petkov <bp@...en8.de>,
Alexei Starovoitov <alexei.starovoitov@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Kees Cook <keescook@...omium.org>,
Josh Poimboeuf <jpoimboe@...hat.com>,
KP Singh <kpsingh@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Florent Revest <revest@...omium.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Christoph Hellwig <hch@...radead.org>
Subject: Re: [PATCH] error-injection: Add prompt for function error
injection
On Tue, 22 Nov 2022 14:51:08 -0500 Chris Mason <clm@...a.com> wrote:
> On 11/22/22 1:29 PM, Steven Rostedt wrote:
> > On Tue, 22 Nov 2022 12:42:33 -0500
> > Chris Mason <clm@...a.com> wrote:
> >
> >> On 11/22/22 5:39 AM, Borislav Petkov wrote:
> >>> On Mon, Nov 21, 2022 at 03:36:08PM -0800, Alexei Starovoitov wrote:
> >>>> The commit log is bogus and the lack of understanding what
Why am I not understanding the controversy here? With this patch
applied, people who want function error injection enable
CONFIG_FUNCTION_ERROR_INJECTION and people who don't want it don't do
that.
Alexei, can you please suggest a less bogus changelog for this?
Powered by blists - more mailing lists