I belive this bug have been fixed when using the precise 3.2 kernels that contain a reworked arch/arm/mm/fault.c
where this part in do_page_fault:
* As per x86, we may deadlock here. However, since the kernel only
* validly references user space from well defined areas of the code,
* we can bug out early if this is from code which shouldn't.
*/
if (!down_read_trylock(&mm->mmap_sem)) {
if (!user_mode(regs) && !search_exception_tables(regs->ARM_pc)) goto no_context;
retry: down_read(&mm->mmap_sem);
have ben changed to remove the retry: label and goto retry: logic.
/*
* As per x86, we may deadlock here. However, since the kernel only
* validly references user space from well defined areas of the code,
* we can bug out early if this is from code which shouldn't.
*/
if (!down_read_trylock(&mm->mmap_sem)) {
if (!user_mode(regs) && !search_exception_tables(regs->ARM_pc))
goto no_context;
down_read(&mm->mmap_sem);
please re-test using https:/ /launchpad. net/ubuntu/ +source/ linux-ti- omap4/3. 2.0-1409. 12
I belive this bug have been fixed when using the precise 3.2 kernels that contain a reworked arch/arm/mm/fault.c
where this part in do_page_fault:
* As per x86, we may deadlock here. However, since the kernel only read_trylock( &mm->mmap_ sem)) { exception_ tables( regs->ARM_ pc))
goto no_context;
down_ read(&mm- >mmap_sem) ;
* validly references user space from well defined areas of the code,
* we can bug out early if this is from code which shouldn't.
*/
if (!down_
if (!user_mode(regs) && !search_
retry:
have ben changed to remove the retry: label and goto retry: logic.
/* read_trylock( &mm->mmap_ sem)) { exception_ tables( regs->ARM_ pc)) read(&mm- >mmap_sem) ;
* As per x86, we may deadlock here. However, since the kernel only
* validly references user space from well defined areas of the code,
* we can bug out early if this is from code which shouldn't.
*/
if (!down_
if (!user_mode(regs) && !search_
goto no_context;
down_