[bug] SLUB & freeing locks [was: Re: 2.6.23-rc1: known regressions with patches]

there's a new regression:

SLUB does not seem to call debug_check_no_locks_freed() - hence on SLUB 
we will not notice certain types of freeing races. (such as freeing an 
object still locked and used on another CPU.) SLAB does this corretly.

	Ingo
-
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] SLUB & freeing locks [was: Re: 2.6.23-rc1: known regressions with patches]
    • From: Peter Zijlstra <[email protected]>

• References:
  • 2.6.23-rc1: known regressions with patches
    • From: Michal Piotrowski <[email protected]>

• Prev by Date: [PATCH] x86-64: Calgary - fix section mismatch warnings in tce
• Next by Date: Re: 2.6.20->2.6.21 - networking dies after random time
• Previous by thread: Re: 2.6.23-rc1: known regressions with patches
• Next by thread: Re: [bug] SLUB & freeing locks [was: Re: 2.6.23-rc1: known regressions with patches]
• 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]