Hi Mohan
I am not allocating memory using GFP_KERNEL, it is always done using
GFP_ATOMIC in my code.
regards
Amit
mohanlal jangir <mohanlal@xxxxxxxxxxx> on 08/24/2004 09:54:21 AM
To: Amit Kumar Singh/HSS@HSS, Kernel Newbies
<kernelnewbies@xxxxxxxxxxxx>
cc:
Subject: Re: Oops kmem_cache_free_one
Looks like you are allocating and freeing GFP_KERNEL memory in interrupt
context. Any memory allocation in interrupt context must be done using
GFP_ATOMIC.
Regards
Mohanlal
----- Original Message -----
From: <aksingh@xxxxxxxxxxx>
To: "Kernel Newbies" <kernelnewbies@xxxxxxxxxxxx>
Sent: Monday, August 23, 2004 7:09 PM
Subject: Oops kmem_cache_free_one
>
> Hi,
>
> While using kfree on a list ndoe being maintained by me, at times I get
a
> Oops message, kfree(node) calls __kmem_cache_free which in turn calls
> kmem_cache_free_one (), the EIP shown in /var/log/messages and ksymoops
> shows the EIP as c012d8fe, this is in kmem_cache_free_one() function.
This
> is difficult to reproduce, hence I am confused as to what may be going
> wrong.
>
> At this EIP what is done is 0xC(%ebx), %ecx
>
> Warning (map_ksym_to_module): cannot match loaded module ext3 to a unique
module object. Trace may not be reliable.
***************** HSS-Unclassified *************
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
