Re: Page Fault Handler Hijacking and Oops

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 8/3/05, Vincenzo Mallozzi <vinjunior@xxxxxxxx> wrote:
> Do you mean only that a kmalloc is needed somewhere in the code or also could
> be some incorrect GFP_flag in some malloc?
> In oder word, I express all the kmalloc with GFP_ATOMIC parameter and I do the
> other malloc operations with vmalloc.

Please reply only to the list; I check it often. This would also allow
everyone to have a better idea about your problem and help you get the
correct answers much quicker.

I am not sure if this error could _also_ be caused by the wrong
kmalloc flag. Maybe someone more experienced in linux-mm could answer
that.

My take is that your code is probably having some issues with the
copy_from_user() or copy_to_user() functions (if you use it) .
Somewhere, the stack is being corrupted leading to a bad EIP. It could
also be that you are sleeping during an interrupt context which
results in "Aiee..".

With your _generalized_ problem,  this is just as general an answer I
could give.

./h
-- 
Operating Systems and Computer Architecture Research  - University of Cincinnati
http://www.ececs.uc.edu/~mohapth

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux