lkml.org 
[lkml]   [1999]   [Aug]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: 2.2.12: kmalloc: Size (4294959124) too large
Date
From
> > 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/

\
 
 \ /
  Last update: 2005-03-22 13:53    [W:0.078 / U:0.224 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site