On Mon, Jan 09, 2012 at 04:22:40PM +0200, Kalle Valo wrote: > On 01/04/2012 12:27 PM, Vasanthakumar Thiagarajan wrote: > > Currently this race is handled but in a messy way an atomic > > variable is being checked in a loop which sleeps upto ms > > in every iteration. Remove this logic and use a mutex > > to make sure irq is not disabled when irq handling is in > > progress. > > > > Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@xxxxxxxxxxxxxxxx> > > Thanks, applied. > > There is one race, though. It's possible that the irq handler is > executed once after the interrupts are disabled. Do we care about that? I don't think so, we read interrupt status only when the interrupts are enabled by checking dev->irq_en_reg.int_status_en in proc_pending_irqs(), so it is already taken care. Vasanth -- 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
