Messages in this thread | | | Date | Fri, 7 Mar 2003 02:22:46 -0500 (EST) | From | Zwane Mwaikambo <> | Subject | Re: Oops: 2.5.64 check_obj_poison for 'size-64' |
| |
On Thu, 6 Mar 2003, Andrew Morton wrote:
> Zwane Mwaikambo <zwane@linuxpower.ca> wrote: > > > > This just popped up on my screen, seems to have been triggered by sar/cron > > (i'll probably have to reboot the box soon) > > > > slab error in check_poison_obj(): cache `size-64': object was modified after freeing > > Call Trace: > > [<c0142226>] check_poison_obj+0x66/0x70 > > [<c0143b92>] kmalloc+0xd2/0x180 > > [<c0166078>] pipe_new+0x28/0xd0 > > [<c0166153>] get_pipe_inode+0x23/0xb0 > > [<c0166212>] do_pipe+0x32/0x1e0 > > [<c0111ed3>] sys_pipe+0x13/0x60 > > [<c010ad9b>] syscall_call+0x7/0xb > > Don't know. If you're using anticipatory scheduler in 2.5.63-mmfoo this > will happen. 64-mm1 is OK.
Nope simply 2.5.64-unwashed. I don't know how to twiddle the advanced knobs
> show_interrupts() is walking the per-irq action chain without locking it. > Any concurrent add/remove activity will explode. > > Do you want to hunt down all the show_interrupts() instances and pop a > spin_lock_irq(desc->lock) around them?
Sure thing.
Thanks, Zwane -- function.linuxpower.ca - 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/
| |