Re: print_vma_addr possible deadlock (was Re: Jeste jeden bug)

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Jiri Kosina <jkosina@...>
Cc: Ingo Molnar <mingo@...>, Thomas Gleixner <tglx@...>, Zdenek Kabelac <zdenek.kabelac@...>, <linux-kernel@...>
Date: Wednesday, February 13, 2008 - 1:13 pm

> > in commit 03252919 you introduced print_vma_addr(), but this funcion for 

Ah yes -- this behaviour of int3 do_trap was always a source of bugs. I remember
fixing such things in this area several times (last time in the RT kernel), but 
I keep forgetting it. Sorry.

The correct fix is to run the int3 and debug handlers on the process stack 
when the fault originated from user space. Then they can run preemptive
and it's ok to schedule for the lock too.

I'll fix that tomorrow.

-Andi
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: Jeste jeden bug, Jiri Kosina, (Wed Feb 13, 12:52 pm)
Re: print_vma_addr possible deadlock (was Re: Jeste jeden bug), Andi Kleen, (Wed Feb 13, 1:13 pm)