[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1548733557.9796.13.camel@mtkswgap22>
Date: Tue, 29 Jan 2019 11:45:57 +0800
From: Miles Chen <miles.chen@...iatek.com>
To: David Rientjes <rientjes@...gle.com>
CC: Christoph Lameter <cl@...ux.com>,
Pekka Enberg <penberg@...nel.org>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
Jonathan Corbet <corbet@....net>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>,
<linux-mediatek@...ts.infradead.org>
Subject: Re: [PATCH v2] mm/slub: introduce SLAB_WARN_ON_ERROR
On Mon, 2019-01-28 at 17:41 -0800, David Rientjes wrote:
> On Thu, 24 Jan 2019, miles.chen@...iatek.com wrote:
>
> > From: Miles Chen <miles.chen@...iatek.com>
> >
> > When debugging slab errors in slub.c, sometimes we have to trigger
> > a panic in order to get the coredump file. Add a debug option
> > SLAB_WARN_ON_ERROR to toggle WARN_ON() when the option is set.
> >
>
> Wouldn't it be better to enable/disable this for all slab caches instead
> of individual caches at runtime? I'm not sure excluding some caches
> because you know they'll WARN and trigger panic_on_warn unnecessarily is
> valid since it could be enabled for that cache as well through this
> interface.
We can enable this option only for specific slab(s).
e.g., slub_debug=W,dentry
or
enable this option for all slabs
e.g., slub_debug=W
Powered by blists - more mailing lists