From: Andreas Herrmann <andreas.herrmann@calxeda.com>
To: Christoph Lameter <cl@linux.com>
Cc: Pekka Enberg <penberg@kernel.org>, Matt Mackall <mpm@selenic.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/slub: Switch slub_debug kernel option to early_param to avoid boot panic
Date: Wed, 6 Nov 2013 20:54:17 +0100 [thread overview]
Message-ID: <20131106195417.GK5661@alberich> (raw)
In-Reply-To: <000001422ed8406b-14bef091-eee0-4e0e-bcdd-a8909c605910-000000@email.amazonses.com>
On Wed, Nov 06, 2013 at 02:16:33PM -0500, Christoph Lameter wrote:
> On Wed, 6 Nov 2013, Andreas Herrmann wrote:
>
> > When I've used slub_debug kernel option (e.g.
> > "slub_debug=,skbuff_fclone_cache" or similar) on a debug session I've
> > seen a panic like:
>
> Hmmm.. That looks like its due to some slabs not having names
> during early boot. kmem_cache_flags is called with NULL as a parameter.
That's because the slub_debug parameter is not evaluated before
kmem_cache_flags is called.
Older kernels didn't show this problem. I think the sequence of those
calls has changed. Not sure what patch set has made that change.
> Are you sure that this fixes the issue? Looks like the
> kmem_cache_flag function should fail regardless of how early you set it.
>
> AFAICT the right fix would be:
That would avoid the panic but I guess it won't enable slub debugging.
However I'll test this.
Andreas
> Subject: slub: Handle NULL parameter in kmem_cache_flags
>
> kmem_cache_flags may be called with NULL parameter during early boot.
> Skip the test in that case.
>
> Signed-off-by: Christoph Lameter <cl@linux.com>
>
> Index: linux/mm/slub.c
> ===================================================================
> --- linux.orig/mm/slub.c 2013-10-15 13:55:44.000000000 -0500
> +++ linux/mm/slub.c 2013-11-06 13:09:21.810583134 -0600
> @@ -1217,7 +1217,7 @@ static unsigned long kmem_cache_flags(un
> /*
> * Enable debugging if selected on the kernel commandline.
> */
> - if (slub_debug && (!slub_debug_slabs ||
> + if (slub_debug && name && (!slub_debug_slabs ||
> !strncmp(slub_debug_slabs, name, strlen(slub_debug_slabs))))
> flags |= slub_debug;
>
>
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-11-06 19:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 18:45 [PATCH] mm/slub: Switch slub_debug kernel option to early_param to avoid boot panic Andreas Herrmann
2013-11-06 19:16 ` Christoph Lameter
2013-11-06 19:21 ` Andreas Herrmann
2013-11-06 19:54 ` Andreas Herrmann [this message]
2013-11-06 20:34 ` Andreas Herrmann
2013-11-06 21:16 ` Andreas Herrmann
2013-11-06 21:38 ` Christoph Lameter
2013-11-07 8:27 ` Andreas Herrmann
2013-11-07 8:41 ` Andreas Herrmann
2013-11-07 16:09 ` Christoph Lameter
[not found] ` <alpine.DEB.2.02.1311071008010.22533@gentwo.org>
2013-11-07 16:29 ` Christoph Lameter
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=20131106195417.GK5661@alberich \
--to=andreas.herrmann@calxeda.com \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=penberg@kernel.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;
as well as URLs for NNTP newsgroup(s).