[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.02.1804231911280.25912@file01.intranet.prod.int.rdu2.redhat.com>
Date: Mon, 23 Apr 2018 19:20:11 -0400 (EDT)
From: Mikulas Patocka <mpatocka@...hat.com>
To: Michal Hocko <mhocko@...nel.org>
cc: Matthew Wilcox <willy@...radead.org>,
David Miller <davem@...emloft.net>,
Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
eric.dumazet@...il.com, edumazet@...gle.com,
bhutchings@...arflare.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, mst@...hat.com, jasowang@...hat.com,
virtualization@...ts.linux-foundation.org, dm-devel@...hat.com,
Vlastimil Babka <vbabka@...e.cz>
Subject: Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
On Mon, 23 Apr 2018, Michal Hocko wrote:
> On Mon 23-04-18 10:24:02, Mikulas Patocka wrote:
>
> > > Really, we have a fault injection framework and this sounds like
> > > something to hook in there.
> >
> > The testing people won't set it up. They install the "kernel-debug"
> > package and run the tests in it.
> >
> > If you introduce a hidden option that no one knows about, no one will use
> > it.
>
> then make sure people know about it. Fuzzers already do test fault
> injections.
I think that in the long term we can introduce a kernel parameter like
"debug_level=1", "debug_level=2", "debug_level=3" that will turn on
debugging features across all kernel subsystems and we can teach users to
use it to diagnose problems.
But it won't work if every subsystem has different debug parameters. There
are 192 distinct filenames in debugfs, if we add 193rd one, harly anyone
notices it.
Mikulas
Powered by blists - more mailing lists