On Fri, Apr 05, 2013 at 12:25:53PM +0200, Jan Kara wrote: > > [ 93.672257] [<ffffffff812c2da9>] sys_msgctl+0x139/0x400 > > [ 93.674641] [<ffffffff816c5d4d>] ? retint_swapgs+0xe/0x13 > > [ 93.677056] [<ffffffff810b6c55>] ? trace_hardirqs_on_caller+0x115/0x1a0 > > [ 93.679626] [<ffffffff8134b39e>] ? trace_hardirqs_on_thunk+0x3a/0x3f > > [ 93.682159] [<ffffffff816cd942>] system_call_fastpath+0x16/0x1b > > [ 93.799329] FIX kmalloc-64: Object at 0xffff88009997e620 not freed > And then sys_msgctl() came and wanted to free it again without > allocating. So it looks like a problem with IPC? Seems plausible, considering the bugs Linus & others found there in the last week. Should be fixed now, so I'll holler if I see this again. thanks, Dave -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
