mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Alok kataria" <alokkataria1@gmail.com>
To: "Christoph Lameter" <clameter@sgi.com>
Cc: "Arjan van de Ven" <arjan@infradead.org>,
	"Linus Torvalds" <torvalds@osdl.org>,
	"Pekka Enberg" <penberg@cs.helsinki.fi>,
	"Ingo Molnar" <mingo@elte.hu>, "Andrew Morton" <akpm@osdl.org>,
	sekharan@us.ibm.com, linux-kernel@vger.kernel.org,
	nagar@watson.ibm.com, balbir@in.ibm.com, alokk@calsoftinc.com
Subject: Re: [patch] lockdep: annotate mm/slab.c
Date: Thu, 13 Jul 2006 16:08:17 -0700	[thread overview]
Message-ID: <35f686220607131608ic63a346p248020b48d4cc734@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0607131520340.30403@schroedinger.engr.sgi.com>

Hi,
On 7/13/06, Christoph Lameter <clameter@sgi.com> wrote:
> On Thu, 13 Jul 2006, Arjan van de Ven wrote:
>
> > there is a corner case in the slab code that I personally don't trust at
> > all. In the NUMA case, if the memory is not originally from your own
> > node, the cache_free_alien() function takes, while having your own local
> > lock, the lock of the remote node as well. (at least on my reading of
> > the code) to free the memory to that node. I have yet to see where in
> > the code it safeguards against that remote node doing the exact same
> > thing in the opposite direction concurrently, and causing a basic ABBA
> > deadlock.
>
> Hmmm.. This case is only followed during bootup when we do not have
> alien caches yet. And its pretty rare to free memory on bootup. Once the
> alien caches are present then we do not take the listlock anymore but
> use the lock of the alien structure.
>

Christoph, IMO even then we wont deadlock, because in the case of a
remote free when there are no alien caches, we simply take the remote
node's list_lock and free the object, directly in the remote slab.

> This could cause an ABBA deadlock if a free happens on another
> processor during bootup before all the slabs are established.
>
> That then brings us to look if a slab free can happen before a slab is
> completely established via kmem_cache_create.
>
> kmem_cache_create takes the cpu hotplug lock and the cache_chain_mutex.
>
> One could argue that a subsystem must make sure that the slab cache it
> creates should not be used before kmem_cache_create is complete?
>
> Alokk: Do we really need to check for alien caches not present there?
>

Yes we do need to, there can be a case when all cpu's of a node have
gone down, we free the alien cache, and this alien cache might have
come from this cache itself, (see cpuup_callback).  In this case we
will find the alien caches to be absent and then we will directly free
to the remote nodes slab.


Thanks & Regards,
Alok
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>


-- 
A computer scientist is someone who, when told to "Go to Hell," sees
the "go to," rather than the destination, as harmful.

Alok Kataria

  reply	other threads:[~2006-07-13 23:08 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 [this message]
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   ` Random panics seen in 2.6.18-rc1 Chandra Seetharaman
2006-07-13 16:05     ` 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=35f686220607131608ic63a346p248020b48d4cc734@mail.gmail.com \
    --to=alokkataria1@gmail.com \
    --cc=akpm@osdl.org \
    --cc=alokk@calsoftinc.com \
    --cc=arjan@infradead.org \
    --cc=balbir@in.ibm.com \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nagar@watson.ibm.com \
    --cc=penberg@cs.helsinki.fi \
    --cc=sekharan@us.ibm.com \
    --cc=torvalds@osdl.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®