Rajkumar Manoharan wrote: > It is safer not to re-enable interrupts on FATAL errors rather than enabling > it and then checking it on irq for bailing out. It would be better if you kill > the interrupts on processing fatal interrupts. I am not sure I understand. The original issue was the race between reset-work and the ISR which resulted in frequent disconnects when a BB-WATCHDOG interrupt occurred or TX hung, which was fixed by introducing the SC_OP_HW_RESET flag. Later, the work_pending() race was fixed. Still, this is a race that can happen and I think fixing it by bypassing the ref-count maintenance and disabling interrupts is okay. Sujith -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
