On 2/10/22 08:16, Zhu Yanjun wrote: > On Thu, Feb 10, 2022 at 3:37 PM Guoqing Jiang <guoqing.jiang@xxxxxxxxx> wrote: >> >> Same as __rxe_add_index, the lock need to be fully IRQ safe, otherwise >> below calltrace appears. >> I had the impression that NAPI ran on a soft IRQ and the rxe tasklets are also on soft IRQs. So at least in theory spin_lock_bh() should be sufficient. Can someone explain where the hard interrupt is coming from that we need to protect. There are other race conditions in current rxe that may also be the cause of this. I am trying to get a patch series accepted to deal with those. Bob
