Steven Dake wrote: > The spinlock is located in the function raid1_alloc_bh. This function > is called by raid1_make_request (spin_lock_irq is safe in this call > path). It is also called by raid1d (spin_lock_irq is unsafe in this > call path, and spin_lock_irqsave should be used instead). Hi Steve, I'm not sure this analysis is correct. raid1_alloc_bh has to reenable interrupts before it allocates memory or goes to sleep, so raid1_alloc_bh had better not be called with interrupts disabled. Also, I don't believe raid1d would have interrupts disabled, given that it's a kernel thread. Thanks, Paul - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
