public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chandra Seetharaman <sekharan@us.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: torvalds@asdl.org, akpm@osdl.org,
	LKML <linux-kernel@vger.kernel.org>,
	Shailabh Nagar <nagar@watson.ibm.com>,
	Balbir Singh <balbir@in.ibm.com>,
	Arjan van de Ven <arjan@infradead.org>
Subject: Re: Random panics seen in 2.6.18-rc1
Date: Thu, 13 Jul 2006 06:51:12 -0700	[thread overview]
Message-ID: <1152798672.18415.2.camel@linuxchandra> (raw)
In-Reply-To: <20060713071221.GA31349@elte.hu>

On Thu, 2006-07-13 at 09:12 +0200, Ingo Molnar wrote:
> * Chandra Seetharaman <sekharan@us.ibm.com> wrote:
> 
> > By adding one patch at a time to 2.6.17's mm/slab.c, I found that the
> > following patch is the cause of the panic.
> > --------------
> > [PATCH] lockdep: annotate SLAB code
> 
> great debugging!

Thanks. 
> 
> I have reviewed that patch, and there's only one chunk that could 
> possibly have a functional effect. The patch below undoes it - does that 
> fix the crashes you are seeing? [If you have lockdep enabled then this 
> patch will cause a lockdep false positive - ignore that one for now, it 
> shouldnt impact the crash scenario itself.]
> 

started the tests with this patch now. will report back in couple of
hours... earlier if it crashes again :), which i doubt.

Thanks & regards,

chandra
> 	Ingo
> 
> --------------------->
> Subject: revert slab.c locking change
> From: Ingo Molnar <mingo@elte.hu>
> 
> Chandra Seetharaman reported SLAB crashes caused by the slab.c
> lock annotation patch. There is only one chunk of that patch
> that has a material effect on the slab logic - this patch
> undoes that chunk.
> 
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> ---
>  mm/slab.c |    9 ---------
>  1 file changed, 9 deletions(-)
> 
> Index: linux/mm/slab.c
> ===================================================================
> --- linux.orig/mm/slab.c
> +++ linux/mm/slab.c
> @@ -3100,16 +3100,7 @@ static void free_block(struct kmem_cache
>  		if (slabp->inuse == 0) {
>  			if (l3->free_objects > l3->free_limit) {
>  				l3->free_objects -= cachep->num;
> -				/*
> -				 * It is safe to drop the lock. The slab is
> -				 * no longer linked to the cache. cachep
> -				 * cannot disappear - we are using it and
> -				 * all destruction of caches must be
> -				 * serialized properly by the user.
> -				 */
> -				spin_unlock(&l3->list_lock);
>  				slab_destroy(cachep, slabp);
> -				spin_lock(&l3->list_lock);
>  			} else {
>  				list_add(&slabp->list, &l3->slabs_free);
>  			}
-- 

----------------------------------------------------------------------
    Chandra Seetharaman               | Be careful what you choose....
              - sekharan@us.ibm.com   |      .......you may get it.
----------------------------------------------------------------------



  parent reply	other threads:[~2006-07-13 13:51 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13  3:59 Random panics seen in 2.6.18-rc1 Chandra Seetharaman
2006-07-13  7:12 ` Ingo Molnar
2006-07-13  7:28   ` Andrew Morton
2006-07-13  7:26     ` Ingo Molnar
2006-07-13  7:44       ` Andrew Morton
2006-07-13  7:46         ` Ingo Molnar
2006-07-13  8:49           ` Ingo Molnar
2006-07-13  8:42         ` Ingo Molnar
2006-07-13  8:46           ` [patch] lockdep: more annotations for mm/slab.c Ingo Molnar
2006-07-13  9:08             ` Andrew Morton
2006-07-13  9:18               ` Ingo Molnar
2006-07-13 10:44                 ` Arjan van de Ven
2006-07-13 10:58                   ` Arjan van de Ven
2006-07-13 12:44         ` [patch] lockdep: undo mm/slab.c annotation Ingo Molnar
2006-07-13 12:46         ` [patch] lockdep: annotate mm/slab.c Ingo Molnar
2006-07-13 15:45           ` Pekka Enberg
2006-07-13 19:55             ` Ingo Molnar
2006-07-13 15:58           ` Pekka Enberg
2006-07-13 18:56             ` Linus Torvalds
2006-07-13 19:21               ` Arjan van de Ven
2006-07-13 22:27                 ` Christoph Lameter
2006-07-13 23:08                   ` Alok kataria
2006-07-13 22:51                 ` Christoph Lameter
2006-07-13 23:16                   ` Andrew Morton
2006-07-14  2:29                     ` Christoph Lameter
2006-07-14  2:46                       ` Christoph Lameter
2006-07-14  3:02                         ` Andrew Morton
2006-07-14  3:35                           ` Christoph Lameter
2006-07-14  3:45                             ` Christoph Lameter
2006-07-14 16:48                               ` Alok kataria
2006-07-14  2:54                       ` Andrew Morton
2006-07-14  2:59                         ` Christoph Lameter
2006-07-13 19:32             ` Ingo Molnar
2006-07-13 18:50           ` Linus Torvalds
2006-07-13 19:06             ` Arjan van de Ven
2006-07-13 19:21               ` Linus Torvalds
2006-07-13 19:26                 ` Arjan van de Ven
2006-07-13 19:17             ` Ingo Molnar
2006-07-13 19:19               ` Ingo Molnar
2006-07-13 21:30             ` Andrew Morton
2006-07-13 13:51   ` Chandra Seetharaman [this message]
2006-07-13 16:05     ` Random panics seen in 2.6.18-rc1 Chandra Seetharaman

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=1152798672.18415.2.camel@linuxchandra \
    --to=sekharan@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=balbir@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nagar@watson.ibm.com \
    --cc=torvalds@asdl.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