Re: [BUG] Lockdep recursive locking in kmem_cache_free

On Fri, 28 Jul 2006, Thomas Gleixner wrote:

> If you need more info, I can add debugs. It happens every bootup.

Could you tell me why _spin_lock and _spin_unlock seem 
to be calling into the slab allocator? Also what is child_rip()? Cannot 
find that function upstream.

There should be no lock recursion here because we are talking about alien 
cache arrays on different nodes.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [BUG] Lockdep recursive locking in kmem_cache_free
    • From: Thomas Gleixner <[email protected]>

• References:
  • [BUG] Lockdep recursive locking in kmem_cache_free
    • From: Thomas Gleixner <[email protected]>
  • Re: [BUG] Lockdep recursive locking in kmem_cache_free
    • From: "Pekka Enberg" <[email protected]>
  • Re: [BUG] Lockdep recursive locking in kmem_cache_free
    • From: Thomas Gleixner <[email protected]>

• Prev by Date: Re: [PATCH] mm: use-once cleanup
• Next by Date: Re: Generic battery interface
• Previous by thread: Re: [BUG] Lockdep recursive locking in kmem_cache_free
• Next by thread: Re: [BUG] Lockdep recursive locking in kmem_cache_free
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]