On Fri, 27 Mar 2009, Philippe Reynes wrote: > Hi all > > I've tried to remove the mlockall(MCL_CURRENT|MCL_FUTURE) > and now, the kernel don't crash. But a data corruption > appear in the data saved by the application. Such corruption > never occurs with other kernel (2.6.28 and 2.6.29). I'll > investigate if it could be an application bug. I don't think that mlockall or the application is the culprit. The bug happens in the middle of the slab cache code. > > server calling Oops: Exception in kernel mode, sig: 5 [#1] PREEMPT > > MPC837x RR605 > > Modules linked in: > > NIP: c0075b08 LR: c0075a50 CTR: c00d7d90 REGS: dbb6dcb0 TRAP: 0700 Not > > tainted (2.6.29-rt1) MSR: 00029032 <EE,ME,CE,IR,DR> CR: 24002488 XER: > > 00000000 TASK = dddea1e0[1769] 'vsftpd' THREAD: dbb6c000 GPR00: 00000001 > > dbb6dd60 dddea1e0 df803e24 df803e10 df803e08 00000000 ddc72020 > > GPR08: 00000000 0000001b dddea1e0 df803e24 24000482 100bf094 00000000 > > c04aa6fc > > GPR16: 00200200 00100100 c04e5958 c04e595c dbb6dd68 c04e0000 c04e0000 > > c04aa6bc > > GPR24: 00000020 dbb6ddd8 00000010 df80ae00 00000000 dbb6de38 df816800 > > df803e00 > > NIP [c0075b08] cache_alloc_refill+0x180/0x62c addr2line -e vmlinux c0075b08 linux-2.6.29/mm/slab.c:3150 That's BUG_ON(slabp->inuse >= cachep->num); > > LR [c0075a50] cache_alloc_refill+0xc8/0x62c > > Call Trace: > > [dbb6dd60] [c038878c] preempt_schedule_irq+0x5c/0x80 (unreliable) Hmm. This one is interesting. Might be we got preempted here - which should be fine, but who knows what we missed when we reworked the locking. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
