Re: kmalloc and other memory allocation failures.

[Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>]

Hi,

Le Thu, 2 Aug 2007 14:22:08 -0600,
Bruce Rowen <browen@xxxxxxxxxxxx> a écrit :

> The failures appear to be similar to something corrupting the stack.  
> My initial impressions are it is somehow related to a change in the  
> kernel that allows parameters to be passed in registers versus on
> the stack (i.e. REGPARM) but I can't find any evidence that I have
> this configured/enabled. The access address it claims to fault on  
> (0x00000001) looks a lot like a register / variable content versus
> an address. Given that my checks of parameters being passed
> to the parent functions (i.e. kmalloc(), register_chrdev()) seem
> fine and the error occurs deep within these functions,
> something/someone must be either corrupting the memory pool base
> address or messing up the stack.

Can you send us your source code ?

Thomas
-- 
Thomas Petazzoni - thomas.petazzoni@xxxxxxxx
http://{thomas,sos,kos}.enix.org - http://www.toulibre.org
http://www.{livret,agenda}dulibre.org

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ