Messages in this thread | | | Subject | Re: 2.2.12: kmalloc: Size (4294959124) too large | Date | Fri, 27 Aug 1999 14:55:54 +0100 (BST) | From | Alan Cox <> |
| |
> > Something tried to allocate negative bytes. > > Yep, but what ? Is there a way to let kmalloc print a stack trace > when this happens? *(int*)0=0; should cause an oops, right ?
On x86 yes
> Duh, I'm booting the same kernel, but now with only that tiny change > to mm/slab.c, there is no kmalloc failure, and I have network connectivity. > Weird.
Once off timing funny ?
> Anyway would the *(int*)0=0; in mm/slab.c be a useful addition to > standard kernels? I've seen the same message on 2.3.13 or so on > my home machine (probably caused by ISDN) and it would be nice to > have a trace of it.
It sounds worth submitting a patch for
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |