On Tue, Aug 25, 2020 at 03:15:03AM +0900, Masami Hiramatsu wrote: > > I did the below, but i'm not at all sure that isn't horrible broken. I > > can't really find many rp->lock sites and this might break things by > > limiting contention. > > This is not enough.
I was afraid of that.. > For checking the recursion of kretprobes, we might > need kretprobe_table_trylock() or kretprobe_table_busy() (but both > can be false positive) Agreed. > Note that rp->lock shouldn't matter unless we will support recursive > kprobe itself. (even though, we can use raw_spin_trylock_irqsave()) If the deadlock mentioned isn't about rp->lock, then what it is about?