Jens Axboe wrote: > We need this in libata to ensure that we don't race between internal > tag usage and the block layer usage. Hmm... I can't think of a race condition. Can you please elaborate what can cause such race condition and how it can get resolved by waiting for in-flight tag? Currently, libata reserves a qc for EH so there won't be any race around it (the old-EH path is broken if invoked with commands in flight anyway, so doesn't matter). Also, as all failed rq's are on hold till EH finishes, if there's a race condition around a tag, it will become a deadlock. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
