mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Boot failure with slab debugging patch
Date: Wed, 10 Aug 2005 10:13:35 -0700	[thread overview]
Message-ID: <20050810101335.61aaddab.akpm@osdl.org> (raw)
In-Reply-To: <15113.1123688409@warthog.cambridge.redhat.com>

David Howells <dhowells@redhat.com> wrote:
>
> This patch in 2.6.13-rc5-mm1:
> 
>  	slab-leak-detector-give-longer-traces.patch
> 
>  Causes the kernel to die with an oops on my test box during boot (see
>  attached), just about here, I think:
> 
>  	static void inline *
>  	cache_alloc_debugcheck_after(kmem_cache_t *cachep,
>  				unsigned int __nocast flags, void *objp, void *caller)
>  	{
>  		if (!objp)	
>  			return objp;
>  		if (cachep->flags & SLAB_POISON) {
>  	#ifdef CONFIG_DEBUG_PAGEALLOC
>  			if ((cachep->objsize % PAGE_SIZE) == 0 && OFF_SLAB(cachep))
>  				kernel_map_pages(virt_to_page(objp), cachep->objsize/PAGE_SIZE, 1);
>  			else
>  				check_poison_obj(cachep, objp);
>  	#else
>  			check_poison_obj(cachep, objp);
>  	#endif
>  			poison_obj(cachep, objp, POISON_INUSE);
>  		}
>  		if (cachep->flags & SLAB_STORE_USER) {
>  			*dbg_userword1(cachep, objp) = caller; /* address(0) */
>  			*dbg_userword2(cachep, objp) = __builtin_return_address(1);
>  --->			*dbg_userword3(cachep, objp) = __builtin_return_address(2);
>  		}
> 
> 
>  Shortly after the call instruction to dbg_userword3().
> 
>  Repealing that patch permits the kernel to work again.

Yup, sorry about that.  For some system calls the __builtin_return_address()
just walks off the top of the stack.

      reply	other threads:[~2005-08-10 17:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-10 15:40 David Howells
2005-08-10 17:13 ` Andrew Morton [this message]

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=20050810101335.61aaddab.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®