Messages in this thread | | | Date | Tue, 23 Jul 2002 13:47:45 -0700 | From | William Lee Irwin III <> | Subject | Re: odd memory corruption in 2.5.27? |
| |
On Tue, Jul 23, 2002 at 01:32:11PM -0700, george anzinger wrote: > I just spent a month tracking down this issue. It comes > down to the slab allocater using per cpu data structures and > protecting them with a combination of interrupt disables and > spin_locks. Preemption is allowed (incorrectly) if > interrupts are off and preempt_count goes to zero on the > spin_unlock. I will wager that this is an SMP machine. > After the preemption interrupts will be on (schedule() does > that) AND you could be on a different cpu. Either of these > is a BAD thing. > The proposed fix is to catch the attempted preemption in > preempt_schedule() and just return if the interrupt system > is off. (Of course there is more that this to it, but I do > believe that the problem is known. You could blow this > assertion out of the water by asserting that the machine is > NOT smp.)
I've been seeing the slab allocator race like mad already (i.e. BUG at slab.c:1947 and slab.c:1961. I'll test this fix.
Thanks, Bill - 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/
| |